XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Medium Medium
    • US Making EHR Data More available for Research and Public Health (MedMorph) (FHIR)
    • 0.1.0
    • Public Health
    • (many)
    • Hide

      This is a Reference Architecture IG which cannot be implemented in the real world by itself without using Content IGs. Some of these Content IGs exist (example Hep C use case) and others would be developed for Cancer and Healthcare survey use cases in the future. The Reference Architecture IG along with the Content IGs are expected to be implementable. However to help the readers there will be additional guidance provided in the Content IG section including an explanation of how to create Content IGs and templates that can be used to capture the workflows and content information required to create the Content IGs.

      In addition the following will be added to the Reference Architecture IG:

      The actual use case descriptions and diagrams will be included in the Reference Architecture IG a downloadable artifact to provide more details and context related to the use case.

      An End to End sequence diagram of a use case flow along with examples for each steps will be added to the Reference Architecture IG. For this purpose the Use Hep C use case will be used an example, so that the eCR IG can be referenced (eICR profiles) for content profiles related to Hep C use case.

      Show
      This is a Reference Architecture IG which cannot be implemented in the real world by itself without using Content IGs. Some of these Content IGs exist (example Hep C use case) and others would be developed for Cancer and Healthcare survey use cases in the future. The Reference Architecture IG along with the Content IGs are expected to be implementable. However to help the readers there will be additional guidance provided in the Content IG section including an explanation of how to create Content IGs and templates that can be used to capture the workflows and content information required to create the Content IGs. In addition the following will be added to the Reference Architecture IG: The actual use case descriptions and diagrams will be included in the Reference Architecture IG a downloadable artifact to provide more details and context related to the use case. An End to End sequence diagram of a use case flow along with examples for each steps will be added to the Reference Architecture IG. For this purpose the Use Hep C use case will be used an example, so that the eCR IG can be referenced (eICR profiles) for content profiles related to Hep C use case.
    • Becky Angeles / Maria Michaels : 33-0-0
    • Correction
    • Compatible, substantive

    Description

      This guide is incomplete and not implementable as written

      This guide states it objective to: "create fully modeled use cases across three distinct areas that are representative of broader areas of research and public health: Chronic Hepatitis C (Hep C) Surveillance, an infectious disease; Cancer Registry Reporting, a chronic disease; and Health Care Surveys, pertaining to health care utilization and not a specific condition. These modeled use cases inform the design of a scalable and extensible reference architecture to facilitate data exchange for key patient-centered research questions and public health information system requirements. For more detailed explanation on the reference architecture refer to Implementation Guide Overview."

      After reading through it, I did not see any fully modeled use cases. Furthermore, although there was ample background, abstract workflows and conformance rules, there was no content describing how this all fits together. For example, I was surprised to see several operations and examples of Messages and Communications resources, because I did not see any reference to FHIR messaging and or use Communication resources or when why and how instances such as these examples are transacted. A more thorough and detailed walk through of the needed transaction to implement this specification and how these artifacts and example fit into the overall picture is needed.

      Attachments

        Activity

          People

            nageshbashyam Nagesh Bashyam
            ehaas Eric Haas
            Eric Haas
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: