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

Consider adding MS datatypes on observation.value[x]

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Medium Medium
    • US QI Core (FHIR)
    • 4.1.0 [deprecated]
    • Clinical Quality Information
    • QICore Observation [deprecated]
    • Hide

      Addressed in FHIR-34537 with additional Must Support references in all QI-Core Observation profiles. Specific to QI Core Observation profile built off of FHIR (I.e., the generic one not associated with a specific US Core profile), in addition to the existing constraints, add the following Must Support elements:

      • subject - Must Support for QICorePatient, QICoreDevice, QICoreLocation
      • effective[x] - Must Support for effectiveDateTime, effectivePeriod, effectiveTiming, effectiveInstant
      • performer - add Must Support for this element and for references QICorePractitioner, QICoreOrganization, QICorePatient, QICoreRelatedPerson
      • value[x] - add MustSupport for valueQuantity, valueCodeableConcept with Preferred binding to US Core Observation Value Codes (SNOMEDCT), valueString, valueBoolean, valueInteger, valueRange, valueRatio, valueTime, valueDateTime, valuePeriod
      • bodySite - change to Preferred binding for SNOMEDCTBodyStructures
      • method - change to Preferred binding for ObservationMethods
      • component.code - change to Preferred binding to LOINC codes
      • value[x] - add MustSupport for valueQuantity, valueCodeableConcept with Preferred binding to US Core Observation Value Codes (SNOMEDCT), valueString, valueBoolean, valueInteger, valueRange, valueRatio, valueTime, valueDateTime, valuePeriod
      Show
      Addressed in FHIR-34537 with additional Must Support references in all QI-Core Observation profiles. Specific to QI Core Observation profile built off of FHIR (I.e., the generic one not associated with a specific US Core profile), in addition to the existing constraints, add the following Must Support elements: subject - Must Support for QICorePatient, QICoreDevice, QICoreLocation effective [x] - Must Support for effectiveDateTime, effectivePeriod, effectiveTiming, effectiveInstant performer - add Must Support for this element and for references QICorePractitioner, QICoreOrganization, QICorePatient, QICoreRelatedPerson value [x] - add MustSupport for valueQuantity, valueCodeableConcept with Preferred binding to US Core Observation Value Codes (SNOMEDCT) , valueString, valueBoolean, valueInteger, valueRange, valueRatio, valueTime, valueDateTime, valuePeriod bodySite - change to Preferred binding for SNOMEDCTBodyStructures method - change to Preferred binding for ObservationMethods component.code - change to Preferred binding to LOINC codes value [x] - add MustSupport for valueQuantity, valueCodeableConcept with Preferred binding to US Core Observation Value Codes (SNOMEDCT) , valueString, valueBoolean, valueInteger, valueRange, valueRatio, valueTime, valueDateTime, valuePeriod
    • Abdulah Rafiqi/Ben Hamlin 13-0-0
    • Enhancement
    • Compatible, substantive

    Description

      The build version of US Core shows three new MS elements on the  

      US Core Laboratory Result Observation Profile

      http://build.fhir.org/ig/HL7/US-Core/StructureDefinition-us-core-observation-lab.html

      valueQuantity

      valueCodeableConcept

      valueString

      Consider if QICore needs to mirror this MS constraint.

      Attachments

        Activity

          People

            feisenberg Floyd Eisenberg
            jrubini Juliet K. Rubini
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: