Jan 2015 Ballot Comment #238

  • Item:operations-top-levelMoreItem:operations-workItem:greenhopper_issue...Item:operations-archiveItem:operations-attach...Item:operations-votesw...Item:operations-subtasksItem:devstatus-cta-listItem:operations-operat...Item:operations-deleteItem:operations-manual...
  • Published
  • AdminItem:operations-fieldsItem:operations-admin-...
  • Item:operations-restore
Item:jira.issue.tools ExportXMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: Medium
    • FHIR Core (FHIR)
    • DSTU1 [deprecated]
    • Modeling & Methodology [deprecated]
    • Datatypes
    • Hide

      Will add "code" to the Identifier type as 0..1 CodeableConcept. ?Binding as "extensible" (must use one of the approved codes if one applies - for interoperability, can supplement with local translations or with additional codes if none of the HL7 codes applies). ?Will add usage notes that the code is not a substitute for "system" and that codes should not be defined that are 1..1 with system. ?Will add the above guidance on what codes will be accepted into the HL7-maintained value set as part of the definition.

      2015/03/09 MnM FHIR call -?Austin/Gordy 5-0-0

      Show
      Will add "code" to the Identifier type as 0..1 CodeableConcept. ?Binding as "extensible" (must use one of the approved codes if one applies - for interoperability, can supplement with local translations or with additional codes if none of the HL7 codes applies). ?Will add usage notes that the code is not a substitute for "system" and that codes should not be defined that are 1..1 with system. ?Will add the above guidance on what codes will be accepted into the HL7-maintained value set as part of the definition. 2015/03/09 MnM FHIR call -?Austin/Gordy 5-0-0
    • Enhancement
    • Compatible, substantive
    • DSTU1 [deprecated]

      Comments
      To ease implementations the core data type definition needs to include a clear identifier type. Maintaining an inventory of URIs globally for particular identifier types is unmanageable. Lack of knowledge of the identifier type will restrict identification methods beyond those needed for the most rudimentary, point-to-point integrations.

      Grahame's Comments
      Agree, discussion on the FHIR List

        1. Identifier Types.docx
          33 kB
        2. Identifier Types.docx
          33 kB

            Panel: location:atl.jira.view.issue.left.context

              Assignee:
              Unassigned
              Reporter:
              Hans Buitendijk
              Hans Buitendijk
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved:

                  Panel: location:atl.jira.view.issue.right.context