Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Current »

The MedMorph track at the upcoming HL7 FHIR Connectathon 34 (9/9 - 9/10 in Phoenix, AZ) is focused on testing the published Health Care Surveys (HCS) IG and a draft RESP-NET on FHIR (RNOF) IG, both of which utilize the MedMorph Reference Architecture IG.

The MedMorph project covers a number of important use cases in the public health arena

  • APIs

  • reporting (eCR Now)

  • efficiency

  • HCS reporting reqs

  • Trail blazers, proposed rule, be at the forefront , help inform NCHS efforts, be a partner, recognition, flexibility to participate virtually, will be required for certification 

    from Cindy Bush to Everyone:    3:26  PM Follows US Core specifically 

    from Prachi to Everyone:    3:26  PM What is the value of the data to NCHS?

    from Prachi to Everyone:    3:26  PM How are the data being used? Helps improve overall efficiency in the future 

    from Prachi to Everyone:    3:27  PM Part of larger DMI effort

    from Prachi to Everyone:    3:27  PM Helps minimize manual processes, etc. 

We are looking for EHR vendors to participate in the track at the Connectathon. In particular, we are looking for vendors willing to:

  • Provide access to a system that can be used during the Connectathon

  • Allow the MedMorph FHIR Backend Service App (the HDEA) to be installed on the system

    • Installation is similar to a SMART on FHIR app

  • Provide assistance with entering data into the system for the use cases to be tested at the Connectathon (or allow for use of data already present on the system)

    • The MedMorph track use case data will be available in spreadsheets (some can be provided in bundles)

    • We are willing to enter the data if that is a option

  • Provide assistance for whatever setup needs to be done to allow the above

    • Security/tokens installation, provide user accounts, etc.

  • Answer questions that arise regarding the use of the system during the Connectathon

  • No labels