Support for multiple versions - 2018-May Core Norm Infrastructure #172

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: Medium
    • FHIR Core (FHIR)
    • STU3
    • FHIR Infrastructure
    • REST (http)
    • 3.1.0.7
    • Hide

      extnsive write up under another task - see http://build.fhir.org/versioning.html. But add this from the versioning API connectathon track to the spec: http://wiki.hl7.org/index.php?title=201801_Versioned_API - see scenario 2 along with specifying the default version

      Show
      extnsive write up under another task - see http://build.fhir.org/versioning.html . But add this from the versioning API connectathon track to the spec: http://wiki.hl7.org/index.php?title=201801_Versioned_API - see scenario 2 along with specifying the default version
    • Grahame Grieve/Rick Geimer: 9-0-0
    • Enhancement
    • Compatible, substantive
    • STU3

      Comment:

      If a system wanted to support multiple versions of the FHIR specification, how should this be handled? Should separate endpoints be created for each version of FHIR supported? Is it possible/desirable to allow the user to hit the same endpoint and ask for the response to be in a version of FHIR that is not the default for the server?

      Summary:

      Support for multiple versions

            Assignee:
            Unassigned
            Reporter:
            Sean McIlvenna
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: