Short Description

Testing the CREDS FHIR IG which healthcare provider organization can use that to automate the collection and formatting the data into a submission, conforming to registry or FHIR implementation guide defined profiles and protocols

Long Description

This FHIR IG is designed as part of an ONC LEAP Grant to promote interoperability between EHR/HIE systems and disease registries with to allow FHIR use to:

  • Define the data needed in a registry submission, relying on existing FHIR resources, profiles, and implementation guides
  • Describe how this data can be collected and organized through FHIR APIs
  • Transform the collected data into content suitable for a registry submission
  • Use applicable FHIR operations defined in existing FHIR Implementation Guides to submit the content
  • Coordinate with other systems to validate and refine registry submissions, as necessary.

Type

Test an Implementation Guide

Related Tracks?


Call for participants

EHR Vendors, HIEs and disease registries

Track Prerequisites


Track Lead(s)

David Pyke 

Track Lead Email(s)

dpyke@ainq.com

Specification Information

https://build.fhir.org/ig/HL7/fhir-registry-protocols-ig/

Zulip stream

https://chat.fhir.org/#streams/320786/CREDS

Track Kick off Call

December 15, 2022, 3:30pm ET

Microsoft Teams meeting
Join on your computer or mobile app

Click here to join the meeting
Or join by entering a meeting ID
Meeting ID: 231 489 381 613
Passcode: g4qK6R
Or call in (audio only)
+1 443-833-0161,,176705784#   United States, Baltimore

Phone Conference ID: 176 705 784#
Find a local number | Reset PIN

Specification Information


System Roles


Testing Scenario:

System roles:

HIE/EHR and Registry

Registry will need to take on the roles of Registry Submission Consumer and Registry Submission Definition Creator.  EHR/HIE will be Registry Submitter and Registry Submission Data Source and will need to have an application that can read the CREDS Structure Definition and create the queries needed to fetch the data and create a submission Bundle


Role 1 Name:

Registry Submission Definition Creator

Scenarios

The Registry Submission Definition Creator manages the definitional artifacts (logical model and transforms) supporting a clinical registry

Scenario Step 1 Name

Action:    Create / Update Registry Definition [CURD]


Precondition: Success Criteria: Registry Submission Definition Repository has the full definition of the registry data requirements in a FHIR StructureDefinition.


Success Criteria:  


Bonus point:


TestScript(s):



Security and Privacy Considerations:

Standard for PHI data

Role 2 Name:

Registry Submitter

Scenarios

The Registry Submission Definition Creator manages the definitional artifacts (logical model and transforms) supporting a clinical registry

Scenario Step 2 Name

Action: Search / Retrieve Registry Definition [SRRD]
Retrieve Registry Submission Data [RRSD]
Create / Update Registry Submission [CURS]



Precondition: Success Criteria: 



Success Criteria:  Registry Submission Consumer has a complete registry submission bundle.



Bonus point: Registry Submission Consumer is able to ingest the bundle



TestScript(s):