Add fhirVersion to Resource

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive
    • Priority: Medium
    • FHIR Core (FHIR)
    • STU3
    • FHIR Infrastructure
    • Normative
    • BaseResource
    • Hide
      • Document the MIME-type parameter as a way to describe the version of the resource in the MIME package.
      • We document the use of a version profile as exampled below in the specification
      • That the product director extends the hosting to make them resolvable.
      • Once resources are published as normative an extension on its structuredefinition marks which version it became normative at.

      <Bundle xmlns="http://hl7.org/fhir">
      <entry>
      <resource>
      <Patient>
      <meta>
      <profile value="http://hl7.org/fhir/1.0/StructureDefinition/Patient"/>
      <profile value="http://hl7.org/fhir/1.4/StructureDefinition/Patient"/>
      <profile value="http://hl7.org/fhir/3.0/StructureDefinition/Patient"/>
      <profile value="http://hl7.org/fhir/4.0/StructureDefinition/Patient"/>
      <profile value="http://hl7.org/fhir/5.0/StructureDefinition/Patient"/>
      </meta>
      </Patient>
      </resource>
      </entry>
      </Bundle>

      This solution is aiming to be a backward compatible solution. As per joint Conformance/FHIR-I meeting at WGM Cologne Wed Q3 it should be documented in R4 that the solution is applicable in DSTU2/STU3 too.

      Show
      Document the MIME-type parameter as a way to describe the version of the resource in the MIME package. We document the use of a version profile as exampled below in the specification That the product director extends the hosting to make them resolvable. Once resources are published as normative an extension on its structuredefinition marks which version it became normative at. <Bundle xmlns=" http://hl7.org/fhir "> <entry> <resource> <Patient> <meta> <profile value=" http://hl7.org/fhir/1.0/StructureDefinition/Patient "/> <profile value=" http://hl7.org/fhir/1.4/StructureDefinition/Patient "/> <profile value=" http://hl7.org/fhir/3.0/StructureDefinition/Patient "/> <profile value=" http://hl7.org/fhir/4.0/StructureDefinition/Patient "/> <profile value=" http://hl7.org/fhir/5.0/StructureDefinition/Patient "/> </meta> </Patient> </resource> </entry> </Bundle> This solution is aiming to be a backward compatible solution. As per joint Conformance/FHIR-I meeting at WGM Cologne Wed Q3 it should be documented in R4 that the solution is applicable in DSTU2/STU3 too.
    • Grahame Grieve/Corey Spears: 20-0-1
    • Enhancement
    • Compatible, substantive
    • STU3

      We need to add FHIR version information to Resource the same data element currently available in StructureDefinition: FHIR version:

      fhirVersion ?0..1 id FHIR Version this StructureDefinition targets All Published FHIR versions (Required)

      This would allow implementers to include FHIR resources as attachments or data objects without RESTful API. It is necesarry to allow the reuse of FHIR with other transports besides REST. This item was discussed at the HL7 WGM in January during a joint Confromance/FHIR-I and this item was recommended to FHIR-I for resolution.

            Assignee:
            Unassigned
            Reporter:
            Ioana Singureanu
            greg_staudenmaier, Ioana Singureanu
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: