Updates of Profiles to FHIR DSTU2: Difference between revisions

From IHE Wiki
Jump to navigation Jump to search
Line 24: Line 24:
** others TBD.
** others TBD.
* Need a consistent way to use FHIR section numbers that are distinct from IHE section numbers. For example when we refer into the FHIR specification (e.g. when referencing the Signature data type we could use "1.19.0.16 Signature", or could use the anchor URL http://hl7.org/fhir/DSTU2/datatypes.html#signature). If using the section numbers (e.g. 1.19.0.16) it needs to be clear that is a FHIR spec number, not an IHE profile number. -- Might we define a prefix "fhir:1.19.0.16"
* Need a consistent way to use FHIR section numbers that are distinct from IHE section numbers. For example when we refer into the FHIR specification (e.g. when referencing the Signature data type we could use "1.19.0.16 Signature", or could use the anchor URL http://hl7.org/fhir/DSTU2/datatypes.html#signature). If using the section numbers (e.g. 1.19.0.16) it needs to be clear that is a FHIR spec number, not an IHE profile number. -- Might we define a prefix "fhir:1.19.0.16"
*  
* more TBD.
* Create a HL7 balloted and published FHIR Profile
* Create a HL7 balloted and published FHIR Profile

Revision as of 11:19, 2 October 2015

This page holds the overall plan for updating the IHE Profiles to FHIR DSTU2.

List of Profiles to be updated

In ITI, Initial work is being done using CPs

  • MHD
  • PDQm
  • PIXm
  • mACM
  • RESTful ATNA Query

In PCC, ????

  • CMAP
  • GAO
  • RECON

Punch List of changes

There are some things that need to be done consistently for all profiles of FHIR. There are other things that need to be unique to each profile. Profile specific changes are managed independently of this punch list.

  • Align on DSTU2 final published http://hl7.org/fhir/DSTU2/index.html
  • Make sure the URLs to the FHIR specification are fully specified and accurate.
  • Need a consistent way to use FHIR section numbers that are distinct from IHE section numbers. For example when we refer into the FHIR specification (e.g. when referencing the Signature data type we could use "1.19.0.16 Signature", or could use the anchor URL http://hl7.org/fhir/DSTU2/datatypes.html#signature). If using the section numbers (e.g. 1.19.0.16) it needs to be clear that is a FHIR spec number, not an IHE profile number. -- Might we define a prefix "fhir:1.19.0.16"
  • more TBD.
  • Create a HL7 balloted and published FHIR Profile