Coordinated Registry Network (CRN) HL7 Implementation Guide (IG) Workgroup (WG)

Meeting Date & Time

Tuesday, May 28, 2019 at 2:00 pm ET

Attendees

Attendees

Present/Absent

Attendees

Present/Absent

Becky Angeles

P

Behnaz  Minaei

X

Nagesh Bashyam (Dragon)

P

JaWanna Henry

P

Gayathri Jayawardena

P

Myron Finseth

P

Richard Ballew

P

Vaishnavi Rao

P

Rob Samples

X

Ioana Singureanu

X

Terrie Reed

P

Marti Velezis

P

Lisa Lang

X

Patrick McLaughlin

P

Abdullah Rafiqi

P

Robin Taylor

P

Christina Nguyen

X

Lindsey Hoggle

P

Craig Newman

P

Mary Ann Hantakas

P

Discussion                                                                    

CRN AUGS FHIR App Demo

  • Dragon presented a demonstration of the app
    • Runs across a variety of platforms, including IPhone, IPad, Android, Android tablet
    • SMART on FHIR app
      • Can interact with EHR or registry
    • Forms Displayed
      • Pre-Operative Information
      • Operative Information Section
      • Short Term Follow Up
      • Long Term Follow Up
    • Example
      • Select patient from list of all patients in registry (patient widget)
      • Patient information displayed
      • Data collection
        • UDI - Scan or manual entry
    • Questions
      • UDI Discussion
        • Terrie Reed suggested discussions are needed to improve the UDI section. 
      • Is the data being collected or has it already been collected and being imported?
        • Data is collected during patient encounter.  If the data is entered in the EHR, the data can be pulled from the EHR.
        • Using NLM open source tools for structured data capture in this app. 
      • Is the UDI scanned?
        • Can manually enter or scan using mobile device
        • Call the GUDID API to populate the information
        • Suggested it would be useful to include functionality in the event the values are not matching what is in front of the provider. 

 

CRN Implementation Guide (IG) Ballot Comment Reconciliation

  • Comment resolutions from last week’s call were added to the tracker
  • Block voting will occur during the bi-weekly BR&R WG calls
  • Comment Review
    • 20789 - Adverse Event capture and make sure right resource is selected
      • This is related to 21016 which was discussed last week (If AdverseEvent is “not specific enough currently” should it be removed from the current IG?).  The group agreed to follow up with the FDA POP Clinical Working Group regarding specific requirements.
      • Craig Newman agreed pointing to the base resource is vague.  Adverse Event is more about risk management rather than the actual thing that occurred that needs managing.  Agreed this can be addressed in conjunction with Tracker Item 21016.
      • Once the data element requirements are identified will need to map accordingly to Condition/Observation or AdverseEvent. 
      • The requirements will depend on the use case: extracting data from another source versus recording the adverse event data.
      • The group noted if there is no consensus on the requirements it will not be included in this version.
      • Resolution: This ticket will be flagged for follow-up per the discussion above.
    • 20790 - Include all codes and value sets for common data elements
      • This is similar to ticket 21015 where the agreed resolution was as follows: Link to the VSAC FHIR API for value sets in the Terminology section.  Include a mention of the license requirements to access the value sets.
      • It was noted that there is a need to verify that the value sets in the spreadsheet are accessible via the API, if not they should be added to the IG.
      • Craig agreed with this resolution.
    • 21017 - use procedure.location instead of location.identifier
      • If trying to collect the facility where the procedure was performed, procedure might be a better resource.
      • Resolution: Will modify mapping of FacilityID to use procedure.location.identifier and the Profile will be procedure-crn.  Will update the Procedure profile to reference the US-Core location for the location data element.

 

Next Steps

  • Comment resolution will continue on next week’s call.