2nd DSTU Draft For Comment
This page is part of the FHIR Specification (v0.4.0: DSTU 2 Draft). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions 
Source for Dictionarynull
<Profile xmlns="http://hl7.org/fhir"> <id value="hspc-QuantitativeLab-dataelements-OxygenPPresPtBldCoVQnLabObs"/> <url value="http://hl7.org/fhir/Profile/OxygenPPresPtBldCoVQnLabObs"/> <name value="HSPC Standard Quantitative Lab: Oxygen"/> <publisher value="HSPC"/> <contact> <telecom> <system value="url"/> <value value="http://healthcaresoa.org"/> </telecom> </contact> <description value="??"/> <status value="draft"/> <date value="2015-02-18"/> <type value="Observation"/> <base value="http://hl7.org/fhir/Profile/observation-hspc-standardlabobs-quantitative-stdqty"/> <snapshot> <element> <path value="Observation"/> <name value="stdqty"/> <short value="Measurements and simple assertions"/> <definition value="Measurements and simple assertions made about a patient, device or other subject."/> <comments value="Used for simple observations such as device measurements, laboratory atomic results, vital signs, height, weight, smoking status, comments, etc. Other resources are used to provide context for observations such as Lab reports, etc."/> <requirements value="Observations are a key aspect of healthcare. This resource is used to capture those that do not require more sophisticated mechanisms."/> <synonym value="Vital Signs"/> <synonym value="Measurement"/> <synonym value="Results"/> <synonym value="Tests"/> <min value="1"/> <max value="1"/> <constraint> <key value="obs-6"/> <name value="data absent reason"/> <severity value="error"/> <human value="Shall only be present if Observation.value[x] is not present"/> <xpath value="not(exists(f:dataAbsentReason)) or (not(exists(*[starts-with(local-name(.), 'value')])))"/> </constraint> <constraint> <key value="inv-1"/> <name value="value or dataAbsentReason"/> <severity value="error"/> <human value="Must have either a value or a dataAbsentReason but not both"/> <xpath value="(f:value or f:dataAbsentReason) and (not(f:value and f:dataAbsentReason))"/> </constraint> <mapping> <identity value="v2"/> <map value="OBX"/> </mapping> <mapping> <identity value="rim"/> <map value="Observation[classCode=OBS, moodCode=EVN]"/> </mapping> </element> <element> <path value="Observation.id"/> <short value="Logical id of this artefact"/> <definition value="The logical id of the resource, as used in the url for the resoure. Once assigned, this value never changes."/> <comments value="The only time that a resource does not have an id is when it is being submitted to the server using a create operation. Bundles always have an id, though it is usually a generated UUID."/> <min value="0"/> <max value="1"/> <type> <code value="id"/> </type> </element> <element> <path value="Observation.meta"/> <short value="Metadata about the resource"/> <definition value="The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content may not always be associated with version changes to the resource."/> <min value="0"/> <max value="1"/> <type> <code value="Meta"/> </type> </element> <element> <path value="Observation.implicitRules"/> <short value="A set of rules under which this content was created"/> <definition value="A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content."/> <comments value="Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element as much as possible."/> <min value="0"/> <max value="1"/> <type> <code value="uri"/> </type> <isModifier value="true"/> </element> <element> <path value="Observation.language"/> <short value="Language of the resource content"/> <definition value="The base language in which the resource is written."/> <comments value="Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute)."/> <min value="0"/> <max value="1"/> <type> <code value="code"/> </type> <binding> <name value="Language"/> <isExtensible value="false"/> <conformance value="required"/> <description value="A human language"/> <referenceUri value="http://tools.ietf.org/html/bcp47"/> </binding> </element> <element> <path value="Observation.text"/> <short value="Text summary of the resource, for human interpretation"/> <definition value="A human-readable narrative that contains a summary of the resource, and may be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety."/> <comments value="Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative."/> <synonym value="narrative"/> <synonym value="html"/> <synonym value="xhtml"/> <synonym value="display"/> <min value="0"/> <max value="1"/> <type> <code value="Narrative"/> </type> <condition value="dom-1"/> <mapping> <identity value="rim"/> <map value="Act.text?"/> </mapping> </element> <element> <path value="Observation.contained"/> <short value="Contained, inline Resources"/> <definition value="These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope."/> <comments value="This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again."/> <synonym value="inline resources"/> <synonym value="anonymous resources"/> <synonym value="contained resources"/> <min value="0"/> <max value="*"/> <type> <code value="Resource"/> </type> <mapping> <identity value="rim"/> <map value="N/A"/> </mapping> </element> <element> <path value="Observation.extension"/> <slicing> <discriminator value="url"/> <ordered value="false"/> <rules value="open"/> </slicing> <short value="Additional Content defined by implementations"/> <definition value="May be used to represent additional information that is not part of the basic definition of the resource. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension."/> <comments value="There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone."/> <synonym value="extensions"/> <synonym value="user content"/> <min value="0"/> <max value="*"/> <type> <code value="Extension"/> </type> <mapping> <identity value="rim"/> <map value="N/A"/> </mapping> </element> <element> <path value="Observation.extension"/> <name value="reportingPriority"/> <short value="Additional Content defined by implementations"/> <definition value="May be used to represent additional information that is not part of the basic definition of the resource. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension."/> <comments value="There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone."/> <synonym value="extensions"/> <synonym value="user content"/> <min value="0"/> <max value="1"/> <type> <code value="Extension"/> <profile value="http://hl7.org/fhir/ExtensionDefinition/hspc-ReportingPriority"/> </type> <mapping> <identity value="rim"/> <map value="N/A"/> </mapping> </element> <element> <path value="Observation.extension"/> <name value="deltaFlag"/> <short value="Additional Content defined by implementations"/> <definition value="May be used to represent additional information that is not part of the basic definition of the resource. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension."/> <comments value="There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone."/> <synonym value="extensions"/> <synonym value="user content"/> <min value="0"/> <max value="1"/> <type> <code value="Extension"/> <profile value="http://hl7.org/fhir/ExtensionDefinition/hspc-DeltaFlag"/> </type> <mapping> <identity value="rim"/> <map value="N/A"/> </mapping> </element> <element> <path value="Observation.extension"/> <name value="verified"/> <short value="Additional Content defined by implementations"/> <definition value="May be used to represent additional information that is not part of the basic definition of the resource. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension."/> <comments value="There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone."/> <synonym value="extensions"/> <synonym value="user content"/> <min value="0"/> <max value="1"/> <type> <code value="Extension"/> <profile value="http://hl7.org/fhir/ExtensionDefinition/hspc-Verified"/> </type> <mapping> <identity value="rim"/> <map value="N/A"/> </mapping> </element> <element> <path value="Observation.extension"/> <name value="updated"/> <short value="Additional Content defined by implementations"/> <definition value="May be used to represent additional information that is not part of the basic definition of the resource. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension."/> <comments value="There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone."/> <synonym value="extensions"/> <synonym value="user content"/> <min value="0"/> <max value="1"/> <type> <code value="Extension"/> <profile value="http://hl7.org/fhir/ExtensionDefinition/hspc-Updated"/> </type> <mapping> <identity value="rim"/> <map value="N/A"/> </mapping> </element> <element> <path value="Observation.extension"/> <name value="indirectTarget"/> <short value="Additional Content defined by implementations"/> <definition value="May be used to represent additional information that is not part of the basic definition of the resource. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension."/> <comments value="There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone."/> <synonym value="extensions"/> <synonym value="user content"/> <min value="0"/> <max value="1"/> <type> <code value="Extension"/> <profile value="http://hl7.org/fhir/ExtensionDefinition/indirectTarget"/> </type> <mapping> <identity value="rim"/> <map value="N/A"/> </mapping> </element> <element> <path value="Observation.modifierExtension"/> <short value="Extensions that cannot be ignored"/> <definition value="May be used to represent additional information that is not part of the basic definition of the resource, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions."/> <comments value="There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone."/> <synonym value="extensions"/> <synonym value="user content"/> <min value="0"/> <max value="*"/> <type> <code value="Extension"/> </type> <mapping> <identity value="rim"/> <map value="N/A"/> </mapping> </element> <element> <path value="Observation.code"/> <short value="Type of observation (code / type)"/> <definition value="Describes what was observed. Sometimes this is called the observation "code"."/> <requirements value="Knowing what kind of observation is being made is essential to understanding the observation."/> <min value="1"/> <max value="1"/> <type> <code value="CodeableConcept"/> </type> <fixedCodeableConcept> <coding> <system value="http://loinc.org"/> <code value="28649-2"/> </coding> </fixedCodeableConcept> <binding> <name value="HSPC-Quantitative-Observations"/> <isExtensible value="true"/> <conformance value="preferred"/> <description value="Standard LOINC codes"/> <referenceReference> <reference value="http://hl7.org/fhir/vs/hspc-QuantitativeLabCodes"/> </referenceReference> </binding> <mapping> <identity value="v2"/> <map value="OBX-3-observation identifier"/> </mapping> <mapping> <identity value="rim"/> <map value="code"/> </mapping> <mapping> <identity value="cdl.key"/> <map value="StandardLabObs_KEY_VALUESET_ECID"/> </mapping> </element> <element> <path value="Observation.valueQuantity"/> <short value="Actual result"/> <definition value="The information determined as a result of making the observation, if the information has a simple value."/> <comments value="Normally, an observation will have either a value or a set of related observations. A few observations (e.g. apgar store) may have both a value and related observations (for apgar, the observations from which the measure is derived). If a value is present, the datatype for this element should be determined by Observation.code. A CodeableConcept with just a text would be used instead of a string if the field was usually coded, or if the type associated with the Observation.code defines a coded value. For boolean values use valueCodeableConcept and select codes from <http://hl7.org/fhir/v2/vs/0136> (These "yes/no" concepts can be mapped to the display name "true/false" or other mutually exclusive terms that may be needed"). The element, Observation.value[x], has a variable name depending on the type as follows: valueQuantity, valueCodeableConcept, valueRatio, valueChoice, valuePeriod, valueSampleData, or valueString (The name format is "'value' + the type name" with a capital on the first letter of the type)."/> <requirements value="An observation exists to have a value, though it may not if it is in error, or it represents a group of observations."/> <min value="0"/> <max value="1"/> <type> <code value="Quantity"/> </type> <mapping> <identity value="v2"/> <map value="OBX.2, OBX.5, OBX.6"/> </mapping> <mapping> <identity value="rim"/> <map value="value"/> </mapping> </element> <element> <path value="Observation.valueQuantity.id"/> <representation value="xmlAttr"/> <short value="xml:id (or equivalent in JSON)"/> <definition value="unique id for the element within a resource (for internal references)."/> <min value="0"/> <max value="1"/> <type> <code value="id"/> </type> <mapping> <identity value="rim"/> <map value="n/a"/> </mapping> </element> <element> <path value="Observation.valueQuantity.extension"/> <short value="Additional Content defined by implementations"/> <definition value="May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension."/> <comments value="There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone."/> <synonym value="extensions"/> <synonym value="user content"/> <min value="0"/> <max value="*"/> <type> <code value="Extension"/> </type> <mapping> <identity value="rim"/> <map value="n/a"/> </mapping> </element> <element> <path value="Observation.valueQuantity.value"/> <short value="Numerical value (with implicit precision)"/> <definition value="The value of the measured amount. The value includes an implicit precision in the presentation of the value."/> <comments value="The implicit precision in the value should always be honored. Monetary values have their own rules for handling precision (refer to standard accounting text books)."/> <requirements value="Precision is handled implicitly in almost all cases of measurement."/> <min value="1"/> <max value="1"/> <type> <code value="decimal"/> </type> <mapping> <identity value="v2"/> <map value="SN.2 / CQ - N/A"/> </mapping> <mapping> <identity value="rim"/> <map value="PQ.value, CO.value, MO.value, IVL.high or IVL.low depending on the value"/> </mapping> </element> <element> <path value="Observation.valueQuantity.comparator"/> <short value="< | <= | >= | > - how to understand the value"/> <definition value="How the value should be understood and represented - whether the actual value is greater or less than the stated value due to measurement issues. E.g. if the comparator is "<" , then the real value is < stated value."/> <comments value="This is labeled as "Is Modifier" because the comparator modifies the interpretation of the value significantly. If there is no comparator, then there is no modification of the value."/> <requirements value="Need a framework for handling measures where the value is <5ug/L or >400mg/L due to the limitations of measuring methodology."/> <min value="0"/> <max value="1"/> <type> <code value="code"/> </type> <isModifier value="true"/> <binding> <name value="QuantityComparator"/> <isExtensible value="false"/> <conformance value="required"/> <description value="How the Quantity should be understood and represented"/> <referenceReference> <reference value="http://hl7.org/fhir/vs/quantity-comparator"/> </referenceReference> </binding> <mapping> <identity value="v2"/> <map value="SN.1 / CQ.1"/> </mapping> <mapping> <identity value="rim"/> <map value="IVL properties"/> </mapping> </element> <element> <path value="Observation.valueQuantity.units"/> <short value="Unit representation"/> <definition value="A human-readable form of the units."/> <requirements value="There are many representations for units and in many contexts, particular representations are fixed and required. I.e. mcg for micrograms."/> <min value="1"/> <max value="1"/> <type> <code value="string"/> </type> <mapping> <identity value="v2"/> <map value="(see OBX.6 etc) / CQ.2"/> </mapping> <mapping> <identity value="rim"/> <map value="PQ.unit"/> </mapping> </element> <element> <path value="Observation.valueQuantity.system"/> <short value="System that defines coded unit form"/> <definition value="The identification of the system that provides the coded form of the unit."/> <requirements value="Need to know the system that defines the coded form of the unit."/> <min value="1"/> <max value="1"/> <type> <code value="uri"/> </type> <fixedUri value="http://unitsofmeasure.org"/> <condition value="qty-3"/> <mapping> <identity value="v2"/> <map value="(see OBX.6 etc) / CQ.2"/> </mapping> <mapping> <identity value="rim"/> <map value="CO.codeSystem, PQ.translation.codeSystem"/> </mapping> </element> <element> <path value="Observation.valueQuantity.code"/> <short value="Coded form of the unit"/> <definition value="A computer processable form of the units in some unit representation system."/> <comments value="The preferred system is UCUM, but SNOMED CT can also be used (for customary units) or ISO 4217 for currency. The context of use may additionally require a code from a particular system."/> <requirements value="Need a computable form of the units that is fixed across all forms. UCUM provides this for quantities, but SNOMED CT provides many units of interest."/> <min value="1"/> <max value="1"/> <type> <code value="code"/> </type> <fixedCode value="mm[Hg]"/> <mapping> <identity value="v2"/> <map value="(see OBX.6 etc) / CQ.2"/> </mapping> <mapping> <identity value="rim"/> <map value="PQ.code, MO.currency, PQ.translation.code"/> </mapping> </element> <element> <path value="Observation.dataAbsentReason"/> <short value="unknown | asked | temp | notasked +"/> <definition value="Provides a reason why the expected value in the element Observation.value[x] is missing."/> <comments value=""Null" or exceptional values can be represented two ways in FHIR Observations. One way is to simply include them in the value set and represent the exceptions in the value. For example, measurement values for a serology test could be "detected", "not detected", "inconclusive", or "test not done". The alternate way is to use the value element for actual observations and use the explicit dataAbsentReason element to record exceptional values. For example, the dataAbsentReason code "error" could be used when the measurement was not completed. Because of these options, use-case agreements are required to interpret general observations for exceptional values."/> <requirements value="For many results it is necessary to handle exceptional values in measurements."/> <min value="0"/> <max value="1"/> <type> <code value="code"/> </type> <exampleCode value="unknown"/> <condition value="obs-6"/> <binding> <name value="DataAbsentReason"/> <isExtensible value="false"/> <conformance value="required"/> <description value="Used to specify why the normally expected content of the data element is missing"/> <referenceReference> <reference value="http://hl7.org/fhir/vs/data-absent-reason"/> </referenceReference> </binding> <mapping> <identity value="v2"/> <map value="N/A"/> </mapping> <mapping> <identity value="rim"/> <map value="value.nullFlavor"/> </mapping> </element> <element> <path value="Observation.interpretation"/> <short value="High, low, normal, etc."/> <definition value="The assessment made based on the result of the observation."/> <requirements value="For some results, particularly numeric results, an interpretation is necessary to fully understand the significance of a result."/> <min value="0"/> <max value="1"/> <type> <code value="CodeableConcept"/> </type> <binding> <name value="CEM_AbnormalInterpretation"/> <isExtensible value="true"/> <conformance value="preferred"/> <description value="See CEM (todo)"/> <referenceReference> <reference value="http://hl7.org/fhir/vs/hspc-Abnormal"/> </referenceReference> </binding> <mapping> <identity value="v2"/> <map value="OBX-8-interpretation codes"/> </mapping> <mapping> <identity value="rim"/> <map value="interpretationCode"/> </mapping> <mapping> <identity value="cdl.key"/> <map value="AbnormalInterpretation_KEY_ECID,OrdinalInterpretation_KEY_ECID"/> </mapping> </element> <element> <path value="Observation.comments"/> <short value="Comments about result"/> <definition value="May include statements about significant, unexpected or unreliable values, or information about the source of the value where this may be relevant to the interpretation of the result."/> <requirements value="Need to be able to provide free text additional information."/> <min value="0"/> <max value="1"/> <type> <code value="string"/> </type> <mapping> <identity value="v2"/> <map value="NTE.3 (partner NTE to OBX, or sometimes another (child?) OBX)"/> </mapping> <mapping> <identity value="rim"/> <map value="subjectOf.observationEvent[code="annotation"].value"/> </mapping> <mapping> <identity value="cdl.key"/> <map value="Comment_KEY_ECID"/> </mapping> </element> <element> <path value="Observation.applies[x]"/> <short value="Physiologically Relevant time/time-period for observation"/> <definition value="The time or time-period the observed value is asserted as being true. For biological subjects - e.g. human patients - this is usually called the "physiologically relevant time". This is usually either the time of the procedure or of specimen collection, but very often the source of the date/time is not known, only the date/time itself."/> <comments value="At least a date should be present unless this observation is a historical report."/> <requirements value="Knowing when an observation was deemed true is important to its relevance as well as determining trends."/> <min value="0"/> <max value="0"/> <type> <code value="dateTime"/> </type> <type> <code value="Period"/> </type> <mapping> <identity value="v2"/> <map value="OBX-14-date/time of the observation, and/or OBX-19 after v2.4 (depends on who observation made)"/> </mapping> <mapping> <identity value="rim"/> <map value="effectiveTime"/> </mapping> <mapping> <identity value="cdl.key"/> <map value="Resulted_ECID"/> </mapping> </element> <element> <path value="Observation.issued"/> <short value="Date/Time this was made available"/> <definition value="The date and time this observation was made available."/> <comments value="Updated when the result is updated."/> <min value="0"/> <max value="1"/> <type> <code value="instant"/> </type> <mapping> <identity value="v2"/> <map value="OBR.22 (or MSH.7), or perhaps OBX-19 (depends on who observation made)"/> </mapping> <mapping> <identity value="rim"/> <map value="participation[typeCode=AUT].time"/> </mapping> </element> <element> <extension url="http://hl7.org/fhir/ExtensionDefinition/profile-display-hint"> <valueString value="default: final"/> </extension> <path value="Observation.status"/> <short value="registered | preliminary | final | amended +"/> <definition value="The status of the result value."/> <requirements value="Need to track the status of individual results - some results are finalised before the whole report is finalised."/> <min value="1"/> <max value="1"/> <type> <code value="code"/> </type> <isModifier value="true"/> <binding> <name value="ObservationStatus"/> <isExtensible value="false"/> <conformance value="required"/> <description value="Codes providing the status of an observation"/> <referenceReference> <reference value="http://hl7.org/fhir/vs/observation-status"/> </referenceReference> </binding> <mapping> <identity value="v2"/> <map value="OBX-11-observation result status"/> </mapping> <mapping> <identity value="rim"/> <map value="status Amended & Final are differentiated by whether it is the subject of a ControlAct event with a type of "revise""/> </mapping> </element> <element> <extension url="http://hl7.org/fhir/ExtensionDefinition/profile-display-hint"> <valueString value="default: ok"/> </extension> <path value="Observation.reliability"/> <short value="ok | ongoing | early | questionable | calibrating | error +"/> <definition value="An estimate of the degree to which quality issues have impacted on the value reported."/> <comments value="Note that in most contexts, unreliable results are not recorded, deleted, or otherwise excluded, but it's not always possible to exclude them from the record. If the reliability indicator is present, interpreters of a result, whether human or machine, should always either be aware of the status or prevented from using the observation without being unaware that the reliability is not "ok"."/> <requirements value="Not all results are completely reliable, and some are still reported anyway."/> <min value="0"/> <max value="1"/> <type> <code value="code"/> </type> <fixedCode value="ok"/> <isModifier value="true"/> <binding> <name value="ObservationReliability"/> <isExtensible value="false"/> <conformance value="required"/> <description value="Codes that provide an estimate of the degree to which quality issues have impacted on the value of an observation"/> <referenceReference> <reference value="http://hl7.org/fhir/vs/observation-reliability"/> </referenceReference> </binding> <mapping> <identity value="v2"/> <map value="Maybe OBX.8/OBX.9"/> </mapping> <mapping> <identity value="rim"/> <map value="uncertaintyCode"/> </mapping> </element> <element> <path value="Observation.bodySite[x]"/> <short value="Observed body part"/> <definition value="Indicates the site on the subject's body where the observation was made ( i.e. the target site)."/> <comments value="Only used if not implicit in code found in Observation.code."/> <requirements value="Knowing where the observation is made is important for tracking if multiple sites are possible."/> <min value="0"/> <max value="0"/> <type> <code value="CodeableConcept"/> </type> <type> <code value="Reference"/> <profile value="http://hl7.org/fhir/Profile/BodySite"/> </type> <binding> <name value="BodySite"/> <isExtensible value="true"/> <conformance value="example"/> <description value="Codes describing anatomical locations. May include laterality"/> <referenceReference> <reference value="http://hl7.org/fhir/vs/body-site"/> </referenceReference> </binding> <mapping> <identity value="v2"/> <map value="OBX-20-observation site"/> </mapping> <mapping> <identity value="rim"/> <map value="targetSiteCode"/> </mapping> </element> <element> <path value="Observation.method"/> <short value="How it was done"/> <definition value="Indicates the mechanism used to perform the observation."/> <comments value="Only used if not implicit in code for Observation.code."/> <requirements value="In some cases, method can impact results and is thus for determining whether results can be compared or determining significance of results."/> <min value="0"/> <max value="0"/> <type> <code value="CodeableConcept"/> </type> <binding> <name value="ObservationMethod"/> <isExtensible value="true"/> <conformance value="example"/> <description value="Methods for simple observations"/> <referenceReference> <reference value="http://hl7.org/fhir/vs/observation-methods"/> </referenceReference> </binding> <mapping> <identity value="v2"/> <map value="OBX-17-observation method"/> </mapping> <mapping> <identity value="rim"/> <map value="methodCode"/> </mapping> </element> <element> <path value="Observation.identifier"/> <short value="Unique Id for this particular observation"/> <definition value="A unique identifier for the simple observation."/> <requirements value="Allows observations to be distinguished and referenced."/> <min value="0"/> <max value="0"/> <type> <code value="Identifier"/> </type> <mapping> <identity value="v2"/> <map value="OBX.21"/> </mapping> <mapping> <identity value="rim"/> <map value="id"/> </mapping> </element> <element> <path value="Observation.subject"/> <short value="Who and/or what this is about"/> <definition value="The patient, or group of patients, location, or device whose characteristics (direct or indirect) are described by the observation and into whose record the observation is placed. Comments: Indirect characteristics may be those of a specimen, fetus, other observer (for example a relative or EMT), or any observation made about the subject."/> <comments value="The only circumstance in which the subject can be missing is when the observation is made by a device that does not know the patient. In this case, the observation SHALL be matched to a patient through some context/channel matching technique, and at this point, the observation should be updated. If the target of the observation is different than the subject, the general extension (http://hl7.org/fhir/ExtensionDefinition/indirectTarget) can be used."/> <requirements value="Observations have no value if you don't know who or what they're about."/> <min value="1"/> <max value="1"/> <type> <code value="Reference"/> <profile value="http://hl7.org/fhir/Profile/Patient"/> </type> <type> <code value="Reference"/> <profile value="http://hl7.org/fhir/Profile/Group"/> </type> <type> <code value="Reference"/> <profile value="http://hl7.org/fhir/Profile/Device"/> </type> <type> <code value="Reference"/> <profile value="http://hl7.org/fhir/Profile/Location"/> </type> <mapping> <identity value="v2"/> <map value="PID-3-patient ID list"/> </mapping> <mapping> <identity value="rim"/> <map value="participation[typeCode=SBJ]"/> </mapping> <mapping> <identity value="cdl.key"/> <map value="Subject_KEY_ECID"/> </mapping> </element> <element> <path value="Observation.specimen"/> <short value="Specimen used for this observation"/> <definition value="The specimen that was used when this observation was made."/> <comments value="Observations are not made on specimens themselves; they are made on a subject, but usually by the means of a specimen. Note that although specimens are often involved, they are not always tracked and reported explicitly. Also note that observation resources are often used in contexts that track the specimen explicitly (e.g. Diagnostic Report)."/> <min value="0"/> <max value="1"/> <type> <code value="Reference"/> <profile value="http://hl7.org/fhir/Profile/hspc-Specimen"/> <aggregation value="contained"/> </type> <mapping> <identity value="rim"/> <map value="participation[typeCode=SPC].specimen"/> </mapping> </element> <element> <path value="Observation.performer"/> <slicing> <discriminator value="performer.type"/> <ordered value="true"/> <rules value="closed"/> </slicing> <short value="Who did the observation"/> <definition value="Who was responsible for asserting the observed value as "true"."/> <requirements value="May give a degree of confidence in the observation and also indicates where follow-up questions should be directed."/> <min value="0"/> <max value="*"/> <type> <code value="Reference"/> <profile value="http://hl7.org/fhir/Profile/Practitioner"/> </type> <type> <code value="Reference"/> <profile value="http://hl7.org/fhir/Profile/Organization"/> </type> <type> <code value="Reference"/> <profile value="http://hl7.org/fhir/Profile/Patient"/> </type> <type> <code value="Reference"/> <profile value="http://hl7.org/fhir/Profile/RelatedPerson"/> </type> <mapping> <identity value="v2"/> <map value="OBX.15 / (Practitioner) OBX-16-responsible observer, PRT-5-participation person:PRT-4-participatio n='RO' / (Device) OBX-18-equipment instance identifier , PRT-10-participation device:PRT-4-particip ation='EQUIP' / (Organization) OBX-23-performing organization name, PRT-8-participation organization:PRT-4-participation='PO'"/> </mapping> <mapping> <identity value="rim"/> <map value="participation[typeCode=PRF]"/> </mapping> </element> <element> <path value="Observation.performer"/> <name value="person"/> <short value="the individual with the primary responsibility for the procedure or action being taken"/> <definition value="the individual with the primary responsibility for the procedure or action being taken."/> <requirements value="May give a degree of confidence in the observation and also indicates where follow-up questions should be directed."/> <min value="0"/> <max value="*"/> <type> <code value="Reference"/> <profile value="http://hl7.org/fhir/Profile/hspc-ResponsibleObserver"/> </type> <mapping> <identity value="v2"/> <map value="OBX.15 / (Practitioner) OBX-16-responsible observer, PRT-5-participation person:PRT-4-participatio n='RO' / (Device) OBX-18-equipment instance identifier , PRT-10-participation device:PRT-4-particip ation='EQUIP' / (Organization) OBX-23-performing organization name, PRT-8-participation organization:PRT-4-participation='PO'"/> </mapping> <mapping> <identity value="rim"/> <map value="participation[typeCode=PRF]"/> </mapping> <mapping> <identity value="cdl.key"/> <map value="ResponsibleObserver_KEY_ECID"/> </mapping> </element> <element> <path value="Observation.performer"/> <name value="lab"/> <short value="name and address of the laboratory that performs the test"/> <definition value="documents the name and address of the laboratory that performs the test. This is a CLIA required item to be printed on the report, CLIA requires the name of the laboratory, city and state of the laboratory."/> <requirements value="May give a degree of confidence in the observation and also indicates where follow-up questions should be directed."/> <min value="0"/> <max value="1"/> <type> <code value="Reference"/> <profile value="http://hl7.org/fhir/Profile/hspc-PerformingLaboratory"/> </type> <mapping> <identity value="v2"/> <map value="OBX.15 / (Practitioner) OBX-16-responsible observer, PRT-5-participation person:PRT-4-participatio n='RO' / (Device) OBX-18-equipment instance identifier , PRT-10-participation device:PRT-4-particip ation='EQUIP' / (Organization) OBX-23-performing organization name, PRT-8-participation organization:PRT-4-participation='PO'"/> </mapping> <mapping> <identity value="rim"/> <map value="participation[typeCode=PRF]"/> </mapping> <mapping> <identity value="cdl.key"/> <map value="PerformingLaboratory_KEY_ECID"/> </mapping> </element> <element> <path value="Observation.device"/> <short value="(Measurement) Device"/> <definition value="The device used to generate the observation data."/> <comments value="An extension should be used if further typing of the device is needed. Devices used to support obtaining an observation can be represented using either extension or through the Observation.related element."/> <min value="0"/> <max value="1"/> <type> <code value="Reference"/> <profile value="http://hl7.org/fhir/Profile/Device"/> </type> <type> <code value="Reference"/> <profile value="http://hl7.org/fhir/Profile/DeviceMetric"/> </type> </element> <element> <path value="Observation.encounter"/> <short value="Healthcare event during which this observation is made"/> <definition value="The healthcare event ( e.g. a patient and healthcare provider interaction ) during which this observation is made."/> <requirements value="For some observations it may be important to know the link between an observation and a particular encounter."/> <min value="0"/> <max value="1"/> <type> <code value="Reference"/> <profile value="http://hl7.org/fhir/Profile/Encounter"/> </type> <mapping> <identity value="v2"/> <map value="PV1"/> </mapping> <mapping> <identity value="rim"/> <map value="Encounter[moodCode=EVN]"/> </mapping> </element> <element> <path value="Observation.referenceRange"/> <short value="Provides guide for interpretation"/> <definition value="Guidance on how to interpret the value by comparison to a normal or recommended range."/> <comments value="Most observations only have one generic reference range. Systems MAY choose to restrict to only supplying the relevant reference range based on knowledge about the patient (e.g. specific to the patient's age, gender, weight and other factors), but this may not be possible or appropriate. Whenever more than one reference range is supplied, the differences between them SHOULD be provided in the reference range and/or age properties."/> <requirements value="Knowing what values are considered "normal" can help evaluate the significance of a particular result. Need to be able to provide multiple reference ranges for different contexts."/> <min value="1"/> <max value="1"/> <constraint> <key value="obs-3"/> <name value="reference range"/> <severity value="error"/> <human value="Must have at least a low or a high or text"/> <xpath value="(exists(f:low) or exists(f:high)or exists(f:text))"/> </constraint> <mapping> <identity value="rim"/> <map value="outboundRelationship[typeCode=REFV]/target[classCode=OBS, moodCode=EVN]"/> </mapping> </element> <element> <path value="Observation.referenceRange.id"/> <representation value="xmlAttr"/> <short value="xml:id (or equivalent in JSON)"/> <definition value="unique id for the element within a resource (for internal references)."/> <min value="0"/> <max value="1"/> <type> <code value="id"/> </type> <mapping> <identity value="rim"/> <map value="n/a"/> </mapping> </element> <element> <path value="Observation.referenceRange.extension"/> <short value="Additional Content defined by implementations"/> <definition value="May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension."/> <comments value="There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone."/> <synonym value="extensions"/> <synonym value="user content"/> <min value="0"/> <max value="*"/> <type> <code value="Extension"/> </type> <mapping> <identity value="rim"/> <map value="n/a"/> </mapping> </element> <element> <path value="Observation.referenceRange.modifierExtension"/> <short value="Extensions that cannot be ignored"/> <definition value="May be used to represent additional information that is not part of the basic definition of the element, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions."/> <comments value="There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone."/> <synonym value="extensions"/> <synonym value="user content"/> <synonym value="modifiers"/> <min value="0"/> <max value="*"/> <type> <code value="Extension"/> </type> <mapping> <identity value="rim"/> <map value="N/A"/> </mapping> </element> <element> <path value="Observation.referenceRange.low"/> <short value="Low Range, if relevant"/> <definition value="The value of the low bound of the reference range. If this element is omitted, the low bound of the reference range is assumed to be meaningless. (e.g. reference range is <2.3) If the low.comparator element is missing, it is assumed to be '>'."/> <min value="0"/> <max value="0"/> <type> <code value="Quantity"/> </type> <condition value="obs-3"/> <condition value="obs-4"/> <constraint> <key value="obs-4"/> <name value="low range comparators"/> <severity value="error"/> <human value="Low range comparators can only be '>' or '>=' or empty"/> <xpath value="not(exists(f:comparator)) or boolean(f:comparator/@value = '<') or boolean(f:comparator/@value = '<=')"/> </constraint> <mapping> <identity value="v2"/> <map value="OBX-7-references range"/> </mapping> <mapping> <identity value="rim"/> <map value="value:IVL_PQ.low"/> </mapping> </element> <element> <path value="Observation.referenceRange.high"/> <short value="High Range, if relevant"/> <definition value="The value of the high bound of the reference range. If this element is omitted, the high bound of the reference range is assumed to be meaningless. (e.g. reference range is > 5) If the low.comparator element is missing , it is assumed to be '<'."/> <min value="0"/> <max value="0"/> <type> <code value="Quantity"/> </type> <condition value="obs-3"/> <condition value="obs-5"/> <constraint> <key value="obs-5"/> <name value="high range comparators"/> <severity value="error"/> <human value="High range comparators can only be '<' or '<=' or empty"/> <xpath value="not(exists(f:comparator)) or boolean(f:comparator/@value = '>') or boolean(f:comparator/@value = '>=')"/> </constraint> <mapping> <identity value="v2"/> <map value="OBX-7-references range"/> </mapping> <mapping> <identity value="rim"/> <map value="value:IVL_PQ.high"/> </mapping> </element> <element> <path value="Observation.referenceRange.meaning"/> <short value="Indicates the meaning/use of this range of this range"/> <definition value="Code for the meaning of the reference range."/> <comments value="This SHOULD be populated if there is more than one range."/> <requirements value="Need to be able to say what kind of reference range this is - normal, recommended, therapeutic, or perhaps what state this reference range applies to (i.e. age, hormonal cycles, etc.)."/> <min value="0"/> <max value="0"/> <type> <code value="CodeableConcept"/> </type> <binding> <name value="ObservationRangeMeaning"/> <isExtensible value="true"/> <conformance value="example"/> <description value="Code for the meaning of a reference range"/> <referenceReference> <reference value="http://hl7.org/fhir/vs/referencerange-meaning"/> </referenceReference> </binding> <mapping> <identity value="v2"/> <map value="OBX-10-nature of abnormal test?"/> </mapping> <mapping> <identity value="rim"/> <map value="interpretationCode"/> </mapping> </element> <element> <path value="Observation.referenceRange.age"/> <short value="Applicable age range, if relevant"/> <definition value="The age at which this reference range is applicable. This is a neonatal age (e.g. number of weeks at term) if the meaning says so."/> <requirements value="Some analytes vary greatly over age."/> <min value="0"/> <max value="0"/> <type> <code value="Range"/> </type> <mapping> <identity value="rim"/> <map value="outboundRelationship[typeCode=PRCN].targetObservationCriterion[code="age"].value"/> </mapping> </element> <element> <path value="Observation.referenceRange.text"/> <short value="Text based reference range in an observation"/> <definition value="Text based reference range in an observation which may be used when a quantitative range is not appropriate for an observation. An example would be a reference value of "Negative" ; or a list or table of 'normals'."/> <min value="1"/> <max value="1"/> <type> <code value="string"/> </type> </element> <element> <path value="Observation.related"/> <short value="Observations related to this observation"/> <definition value="Related observations - either components, or previous observations, or statements of derivation."/> <comments value="Normally, an observation will have either a value or a set of related observations. A few observations (e.g. apgar store) may have both a value and related observations (for apgar, the observations from which the measure is derived)."/> <requirements value="Some observations have important relationships to other observations (e.g Blood Pressure = systolic + diastolic), or are derived from other observations (e.g. calculated apgar score)."/> <min value="0"/> <max value="0"/> <mapping> <identity value="v2"/> <map value="Relationships established by OBX-4 usage"/> </mapping> <mapping> <identity value="rim"/> <map value="outBoundRelationship"/> </mapping> </element> <element> <path value="Observation.related.id"/> <representation value="xmlAttr"/> <short value="xml:id (or equivalent in JSON)"/> <definition value="unique id for the element within a resource (for internal references)."/> <min value="0"/> <max value="1"/> <type> <code value="id"/> </type> <mapping> <identity value="rim"/> <map value="n/a"/> </mapping> </element> <element> <path value="Observation.related.extension"/> <short value="Additional Content defined by implementations"/> <definition value="May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension."/> <comments value="There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone."/> <synonym value="extensions"/> <synonym value="user content"/> <min value="0"/> <max value="*"/> <type> <code value="Extension"/> </type> <mapping> <identity value="rim"/> <map value="n/a"/> </mapping> </element> <element> <path value="Observation.related.modifierExtension"/> <short value="Extensions that cannot be ignored"/> <definition value="May be used to represent additional information that is not part of the basic definition of the element, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions."/> <comments value="There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone."/> <synonym value="extensions"/> <synonym value="user content"/> <synonym value="modifiers"/> <min value="0"/> <max value="*"/> <type> <code value="Extension"/> </type> <mapping> <identity value="rim"/> <map value="N/A"/> </mapping> </element> <element> <path value="Observation.related.type"/> <short value="has-component | has-member | derived-from | sequel-to | replaces | qualified-by | interfered-by"/> <definition value="A code specifying the kind of relationship that exists with the target observation."/> <comments value="A relationship type SHOULD be provided. If the relationship type is "COMP" (composed), then the observation should not be displayed/interpreted in the absence of the related observations."/> <requirements value="May need to indicate whether this observation is composed of others, or merely derived from them."/> <min value="0"/> <max value="1"/> <type> <code value="code"/> </type> <binding> <name value="ObservationRelationshipType"/> <isExtensible value="false"/> <conformance value="required"/> <description value="Codes specifying how two observations are related"/> <referenceReference> <reference value="http://hl7.org/fhir/vs/observation-relationshiptypes"/> </referenceReference> </binding> <mapping> <identity value="v2"/> <map value="N/A"/> </mapping> <mapping> <identity value="rim"/> <map value=".typeCode"/> </mapping> </element> <element> <path value="Observation.related.target"/> <short value="Observation that is related to this one"/> <definition value="A reference to the observation that is related to this observation."/> <min value="1"/> <max value="1"/> <type> <code value="Reference"/> <profile value="http://hl7.org/fhir/Profile/Observation"/> </type> <mapping> <identity value="rim"/> <map value=".targetObservation"/> </mapping> </element> </snapshot> <differential> <element> <path value="Observation.code"/> <fixedCodeableConcept> <coding> <system value="http://loinc.org"/> <code value="28649-2"/> </coding> </fixedCodeableConcept> </element> <element> <path value="Observation.valueQuantity.code"/> <min value="1"/> <max value="1"/> <fixedCode value="mm[Hg]"/> </element> </differential> </Profile>
Usage note: every effort has been made to ensure that the examples are correct and useful, but they are not a normative part of the specification.
© HL7.org 2011+. FHIR DSTU (v0.4.0-4167) generated on Mon, Feb 23, 2015 09:18+1100.
Links: What's a DSTU? |
Version History |
Compare to DSTU1 |
|
Propose a change