Uploaded image for project: 'FHIR Specification Feedback'
  1. FHIR Specification Feedback
  2. FHIR-21163

URI Correction

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Medium Medium
    • US Quality Measures (FHIR)
    • STU3
    • Clinical Quality Information
    • ImplementationGuide [deprecated]
    • Hide

      For code systems, the system and version are specified independently within FHIR, so the last sentence of the conformance requirement needs to be updated to say:

      The Code System declaration MAY include a version

      Rather than The URI MAY include a version.

      Show
      For code systems, the system and version are specified independently within FHIR, so the last sentence of the conformance requirement needs to be updated to say: The Code System declaration MAY include a version Rather than The URI MAY include a version.
    • Bryn Rhodes/Ben Hamlin: 16-0-0
    • Enhancement
    • Non-substantive

    Description

      Could you have:

      codesystem "SNOMEDCT:2017-09": 'http://snomed.info/sct/731000124108/version/201709'

      so that the version is incorporated in the main URI (as stated in the conformance statement). And if so, are vendors/tooling/etc. expected to check both this URI and the version attribute for versioning? What should the behavior be if these point to different versions? Which takes precendence? Is there a "SHOULD" way of doing this?

      Attachments

        Activity

          People

            Unassigned Unassigned
            lizzie_charbonneau Lizzie Charbonneau
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: