2015May core #1370 - Medication Prescription Status Values

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: Medium
    • FHIR Core (FHIR)
    • DSTU1 [deprecated]
    • Terminology Infrastructure
    • DetectedIssue
    • 4.10
    • Hide

      Disposition:?
      1. Where FHIR is defining value sets that are schema bound, the general policy is that we define our own codes with mappings to v2 and v3 (or other) code systems where ever possible. This value set will be changed to an internal one to resolve this particular issue.

      2. FHIR tooling will be written to identify duplicate internally defined code systems, and that they be reconciled by core

      3. Vocab will develop policies for handling ballot input on v2 and v3 code systems and value sets

      Show
      Disposition:? 1. Where FHIR is defining value sets that are schema bound, the general policy is that we define our own codes with mappings to v2 and v3 (or other) code systems where ever possible. This value set will be changed to an internal one to resolve this particular issue. 2. FHIR tooling will be written to identify duplicate internally defined code systems, and that they be reconciled by core 3. Vocab will develop policies for handling ballot input on v2 and v3 code systems and value sets
    • Grahame Grieve / Rob Hausam: 13-0-1
    • Enhancement
    • Non-compatible
    • DSTU1 [deprecated]

      Existing Wording: ContraindicationSeverity

      H, L, M

      Proposed Wording: ContraindicationSeverity

      High, Medium, Low

      Comment:

      Value set incomplete not like other value sets such as MedicationPrescriptionStatus.

      I would expect to see values from FHIR such as high, moderate, and low instead of H,M, and L.

      Also the completed documentation for the value set should include mappings from HL7 v2 and v3.

            Assignee:
            Unassigned
            Reporter:
            Tim McNeil
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: