StructureDefinition-us-core-observation-clinical-result

Sourcehl7.fhir.us.core#current:US Core Implementation Guide (v4.0.1)
resourceTypeStructureDefinition
idus-core-observation-clinical-result
canonicalhttp://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-clinical-result
version7.0.0-ballot
statusactive
publisherHL7 International - Cross-Group Projects
nameUSCoreObservationClinicalResultProfile
titleUS Core Observation Clinical Result Profile
date2022-04-20
descriptionThe US Core Observation Clinical Result Profile is based upon the core FHIR Observation Resource and, along with the US Core DiagnosticReport Profile, meets the US Core Data for Interoperability (USCDI) requirements for *Diagnostic Imaging* and *Clinical Tests* Data Classes. This profile sets minimum expectations for the Observation resource to record and search non-laboratory clinical test results (e.g., radiology and other clinical observations generated from procedures). An example would be when a gastroenterologist reports the size of a polyp observed during a colonoscopy. This profile is the basis for the US Core Laboratory Result Observation Profile, which defines additional data elements to record and search laboratory test results. The US Core Observation Clinical Result Profile sets minimum expectations to promote interoperability and adoption through common implementation. It identifies which core elements, extensions, vocabularies, and value sets **SHALL** be present in the resource and constrains the way the elements are used when using this profile. It provides the floor for standards development for specific use cases.
copyrightUsed by permission of HL7 International, all rights reserved Creative Commons License
jurisdictionsus
fhirVersion4.0.1
kindresource
abstractfalse
sdTtypeObservation
derivationconstraint
basehttp://hl7.org/fhir/StructureDefinition/Observation
Usages
Name Flags Card. Type Description & Constraints doco
. . Observation C Observation us-core-2: If there is no component or hasMember element then either a value[x] or a data absent reason must be present
. . . status S (USCDI) registered | preliminary | final | amended +
. . . Slices for category S 1 .. (USCDI) Classification of type of observation
Slice: Unordered, Open by pattern:$this
. . . . category:us-core S (USCDI) Classification of type of observation
Binding: US Core Clinical Result Observation Category ( required ): Note that other codes are permitted, see Required Bindings When Slicing by Value Sets

. . . code S (USCDI) Clinical Test or Procedure Name
Binding: todo ( extensible )
. . . subject S 1.. Reference (US Core Patient Profile) (USCDI) Who and/or what the observation is about
. . . effective[x] S C (USCDI) Clinically relevant time/time-period for observation
us-core-1: Datetime must be at least to day.
. . . . effectiveDateTime dateTime S
. . . . effectivePeriod Period
. . . . effectiveTiming Timing
. . . . effectiveInstant instant
. . . value[x] S C (USCDI) Result Value
us-core-3: SHALL use UCUM for coded quantity units.
. . . . valueQuantity Quantity S
. . . . valueCodeableConcept CodeableConcept S
. . . . valueString string S
. . . . valueBoolean boolean
. . . . valueInteger integer
. . . . valueRange Range
. . . . valueRatio Ratio
. . . . valueSampledData SampledData
. . . . valueTime time
. . . . valueDateTime dateTime
. . . . valuePeriod Period
. . . dataAbsentReason S C (USCDI) Why the result is missing

doco Documentation for this format

Produced 08 Sep 2023