This content is too valuable to be buried in a single DaVinci IG

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Not Persuasive
    • Priority: Highest
    • US Da Vinci HRex (FHIR)
    • current
    • Clinical Interoperability Council
    • Approaches to Exchanging FHIR Data
    • 3
    • Hide

      As noted clearly in the section, all of the section on 'exchanging' is expected to migrate to the FHIR Core specification. It is published in the Hrex IG for now because the next release of FHIR isn't coming out for another 1.5 years and Da Vinci needed the content sooner.

      Show
      As noted clearly in the section, all of the section on 'exchanging' is expected to migrate to the FHIR Core specification. It is published in the Hrex IG for now because the next release of FHIR isn't coming out for another 1.5 years and Da Vinci needed the content sooner.
    • Marti Velezis / James Tcheng : 6-0-1

      This content is too valuable to be buried in a single DaVinci IG, though I understand that putting it here as a first pass is an easy way to get started.

      I recommend spliting this into a generally applicable set of architectural best principles and a distinct discussion of which pattern works best for HREX. The general principles should be somewhere in the Architects introduction to FHIR http://hl7.org/fhir/overview-arch.html while the HREX specific material should be here in the HREX IG.

            Assignee:
            Unassigned
            Reporter:
            Hugh Glover
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: