| Left: | US Core Head Circumference Profile (http://hl7.org/fhir/us/core/StructureDefinition/us-core-head-circumference) |
| Right: | Personal Functioning and Engagement Collection (http://hl7.org/fhir/us/pacio-pfe/StructureDefinition/pfe-collection) |
| Error | StructureDefinition.url | Values for url differ: 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-head-circumference' vs 'http://hl7.org/fhir/us/pacio-pfe/StructureDefinition/pfe-collection' |
| Error | StructureDefinition.version | Values for version differ: '7.0.0-ballot' vs '1.0.0' |
| Information | StructureDefinition.name | Values for name differ: 'USCoreHeadCircumferenceProfile' vs 'PFECollection' |
| Information | StructureDefinition.title | Values for title differ: 'US Core Head Circumference Profile' vs 'Personal Functioning and Engagement Collection' |
| Information | StructureDefinition.status | Values for status differ: 'active' vs 'draft' |
| Information | StructureDefinition.date | Values for date differ: '2023-10-17' vs '2024-01-05T16:57:50+00:00' |
| Information | StructureDefinition.publisher | Values for publisher differ: 'HL7 International / Cross-Group Projects' vs 'HL7 International / Patient Care' |
| Error | StructureDefinition.baseDefinition | Values for baseDefinition differ: 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-vital-signs' vs 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-survey' |
| Information | StructureDefinition.short | Values for short differ: 'US Core Head Circumference Profile' vs 'Survey Observation' |
| Information | StructureDefinition.short | Values for short differ: 'Additional content defined by implementations' vs 'Extension' |
| Information | StructureDefinition.definition | Values for definition differ: 'May be used to represent additional information that is not part of the basic definition of the resource. 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 can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.' vs 'An Extension' |
| Information | StructureDefinition.requirements | Values for requirements differ: 'Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://hl7.org/fhir/extensibility.html#modifierExtension).' vs 'Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://hl7.org/fhir/R4/extensibility.html#modifierExtension).' |
| Information | StructureDefinition.comment | Values for comment differ: 'To link an Observation to an Encounter use `encounter`. See the [Notes](http://hl7.org/fhir/observation.html#obsgrouping) below for guidance on referencing another Observation.' vs 'To link an Observation to an Encounter use `encounter`. See the [Notes](http://hl7.org/fhir/R4/observation.html#obsgrouping) below for guidance on referencing another Observation.' |
| Information | StructureDefinition.short | Values for short differ: 'registered | preliminary | final | amended +' vs 'Should have the value 'final' when all the observatons are complete and there are no further actions needed. Otherwise, another value from the value set may appropriately be used.' |
| Information | StructureDefinition.requirements | Values for requirements differ: 'Used for filtering what observations are retrieved and displayed.' vs 'To identify that observation is derived from a questionnaire, is related to personal functioning and engagement, and optionally to identify the domain(s) it falls under.' |
| Information | Observation.category | Element minimum cardinalities differ: '1' vs '2' |
| Information | StructureDefinition.short | Values for short differ: 'Head Circumference' vs 'For a Post-Acute Care structured assessment resource such as an instrument or screen, use a LOINC code to identify the instrument/screen name or panel/section title to indicate the kind of assessment.' |
| Information | StructureDefinition.definition | Values for definition differ: 'Coded Responses from C-CDA Vital Sign Results.' vs 'Describes what was observed. Sometimes this is called the observation 'name'.' |
| Information | StructureDefinition.requirements | Values for requirements differ: '5. SHALL contain exactly one [1..1] code, where the @code SHOULD be selected from ValueSet HITSP Vital Sign Result Type 2.16.840.1.113883.3.88.12.80.62 DYNAMIC (CONF:7301).' vs 'Knowing what kind of observation is being made is essential to understanding the observation.' |
| Information | StructureDefinition.comment | Values for comment differ: 'Typically, an observation is made about the subject - a patient, or group of patients, location, or device - and the distinction between the subject and what is directly measured for an observation is specified in the observation code itself ( e.g., 'Blood Glucose') and does not need to be represented separately using this element. Use `specimen` if a reference to a specimen is required. If a code is required instead of a resource use either `bodysite` for bodysites or the standard extension [focusCode](http://hl7.org/fhir/extension-observation-focuscode.html).' vs 'Typically, an observation is made about the subject - a patient, or group of patients, location, or device - and the distinction between the subject and what is directly measured for an observation is specified in the observation code itself ( e.g., 'Blood Glucose') and does not need to be represented separately using this element. Use `specimen` if a reference to a specimen is required. If a code is required instead of a resource use either `bodysite` for bodysites or the standard extension [focusCode](http://hl7.org/fhir/R4/extension-observation-focuscode.html).' |
| Information | StructureDefinition.short | Values for short differ: 'Often just a dateTime for Vital Signs' vs 'Clinical relevant time for an assessment such as post-acute care observations performed with structured evaluation tools is the time the evaluation occurs, i.e., when the clinician obtains the answers entered in the tool. However, the only timing available may be when then tool is completed by the clinician. That timing is generally documented as a point in time (dateTime).' |
| Information | StructureDefinition.definition | Values for definition differ: 'Often just a dateTime for Vital Signs.' vs 'Clinical relevant time for an assessment such as post-acute care observations performed with structured evaluation tools is the time the evaluation occurs, i.e., when the clinician obtains the answers entered in the tool. However, the only timing available may be when then tool is completed by the clinician. That timing is generally documented as a point in time (dateTime).' |
| Information | StructureDefinition.comment | Values for comment differ: 'At least a date should be present unless this observation is a historical report. For recording imprecise or 'fuzzy' times (For example, a blood glucose measurement taken 'after breakfast') use the [Timing](http://hl7.org/fhir/datatypes.html#timing) datatype which allow the measurement to be tied to regular life events.' vs 'The use of effective[x] and dateTime versus Period is subject to implementer workflow and needs. In most situations, an observation is considered as a point in time, even if the assessment occurred over a period of time. Period is included in this implementation guide to provide additional flexibility for specific use cases. However, it is expected most observations will be recorded using DateTime. Furthermore, any retrieval of information should return the relevant if DateTime is requested, even if the original observation was recorded as a period. Some implementers may choose to use additional functions in there retrieves to 'normalize' intervals, as is done in Clinical Quality Language (CQL).' |
| Information | StructureDefinition.comment | Values for comment differ: 'For Observations that don’t require review and verification, it may be the same as the [`lastUpdated` ](http://hl7.org/fhir/resource-definitions.html#Meta.lastUpdated) time of the resource itself. For Observations that do require review and verification for certain updates, it might not be the same as the `lastUpdated` time of the resource itself due to a non-clinically significant update that doesn’t require the new version to be reviewed and verified again.' vs 'For Observations that don’t require review and verification, it may be the same as the [`lastUpdated` ](http://hl7.org/fhir/R4/resource-definitions.html#Meta.lastUpdated) time of the resource itself. For Observations that do require review and verification for certain updates, it might not be the same as the `lastUpdated` time of the resource itself due to a non-clinically significant update that doesn’t require the new version to be reviewed and verified again.' |
| Information | StructureDefinition.short | Values for short differ: 'Who is responsible for the observation' vs 'The person who performed the assessment. The preferred way to specify the performer is to use the PractitionerRole resource to provide both the practitioner and organization.' |
| Warning | Observation.performer | Elements differ in definition for mustSupport: 'false' vs 'true' |
| Information | Observation.performer | Element minimum cardinalities differ: '0' vs '1' |
| Information | StructureDefinition.short | Values for short differ: 'Vital Signs Value' vs 'Actual result' |
| Information | StructureDefinition.definition | Values for definition differ: 'Vital Signs value are typically recorded using the Quantity data type.' vs 'The information determined as a result of making the observation, if the information has a simple value.' |
| Information | StructureDefinition.comment | Values for comment differ: 'An observation may have; 1) a single value here, 2) both a value and a set of related or component values, or 3) only a set of related or component values. 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 additional guidance, see the [Notes section](http://hl7.org/fhir/observation.html#notes) below.' vs 'An observation may have a value if it represents an individual survey question and answer pair. An observation should not have a value if it represents a multi-question survey or multi-select “check all that apply” question. 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.' |
| Information | StructureDefinition.requirements | Values for requirements differ: '9. SHALL contain exactly one [1..1] value with @xsi:type='PQ' (CONF:7305).' vs 'An observation exists to have a value, though it might not if it is in error, or if it represents a group of observations.' |
| Information | Observation.value[x] | Element maximum cardinalities differ: '1' vs '0' |
| Information | StructureDefinition.comment | Values for comment differ: '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 'specimen unsatisfactory'. 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. Note that an observation may only be reported if there are values to report. For example differential cell counts values may be reported only when > 0. Because of these options, use-case agreements are required to interpret general observations for null or exceptional values.' vs ''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. The alternate way is to use the value element for actual observations and use the explicit dataAbsentReason element to record exceptional values. For a given LOINC question, if the LOINC answer list includes concepts such as 'unknown' or 'not available', they should be used for Observation.value. Where these concepts are not part of the value set for Observation.value, the Observation.dataAbsentReason can be used if necessary and appropriate.' |
| Information | StructureDefinition.comment | Values for comment differ: 'Only used if not implicit in code found in Observation.code. In many systems, this may be represented as a related observation instead of an inline component. If the use case requires BodySite to be handled as a separate resource (e.g. to identify and track separately) then use the standard extension[ bodySite](http://hl7.org/fhir/extension-bodysite.html).' vs 'Only used if not implicit in code found in Observation.code. In many systems, this may be represented as a related observation instead of an inline component. If the use case requires BodySite to be handled as a separate resource (e.g. to identify and track separately) then use the standard extension[ bodySite](http://hl7.org/fhir/R4/extension-bodysite.html).' |
| Information | StructureDefinition.requirements | Values for requirements differ: 'Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://hl7.org/fhir/extensibility.html#modifierExtension).' vs 'Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://hl7.org/fhir/R4/extensibility.html#modifierExtension).' |
| Information | StructureDefinition.short | Values for short differ: 'Used when reporting vital signs panel components' vs 'Each post-acute care observation in the collection. May also be another collection to support nested sections.' |
| Information | StructureDefinition.definition | Values for definition differ: 'Used when reporting vital signs panel components.' vs 'Aggregate set of Observations that represent question answer pairs for both multi-question surveys and multi-select questions.' |
| Information | StructureDefinition.comment | Values for comment differ: 'When using this element, an observation will typically have either a value or a set of related resources, although both may be present in some cases. For a discussion on the ways Observations can assembled in groups together, see [Notes](http://hl7.org/fhir/observation.html#obsgrouping) below. Note that a system may calculate results from [QuestionnaireResponse](http://hl7.org/fhir/questionnaireresponse.html) into a final score and represent the score as an Observation.' vs 'This grouping element is used to represent surveys that group several questions together or individual questions with “check all that apply” responses. For example in the simplest case a flat multi-question survey where the 'panel' observation is the survey instrument itself and instead of an `Observation.value` the `hasMember` element references other Observation that represent the individual questions answer pairs. In a survey that has a heirarchical grouping of questions, the observation 'panels' can be nested. Because surveys can be arbitrarily complex structurally, not all survey structures can be represented using this Observation grouping pattern.' |
| Warning | Observation.hasMember | Elements differ in definition for mustSupport: 'false' vs 'true' |
| Error | Observation.hasMember | Type Mismatch: Reference([CanonicalType[http://hl7.org/fhir/StructureDefinition/QuestionnaireResponse], CanonicalType[http://hl7.org/fhir/StructureDefinition/MolecularSequence], CanonicalType[http://hl7.org/fhir/StructureDefinition/vitalsigns]]) vs Reference([CanonicalType[http://hl7.org/fhir/us/pacio-pfe/StructureDefinition/pfe-observation-single]]) |
| Information | StructureDefinition.short | Values for short differ: 'Related measurements the observation is made from' vs 'Should point back to the QuestionnaireResponse that this resource is derived from.' |
| Information | StructureDefinition.definition | Values for definition differ: 'The target resource that represents a measurement from which this observation value is derived. For example, a calculated anion gap or a fetal measurement based on an ultrasound image.' vs 'Observations or QuestionnaireResponses from which this observation value is derived.' |
| Information | StructureDefinition.comment | Values for comment differ: 'All the reference choices that are listed in this element can represent clinical observations and other measurements that may be the source for a derived value. The most common reference will be another Observation. For a discussion on the ways Observations can assembled in groups together, see [Notes](http://hl7.org/fhir/observation.html#obsgrouping) below.' vs 'All the reference choices that are listed in this element can represent clinical observations and other measurements that may be the source for a derived value. The most common reference will be another Observation. For a discussion on the ways Observations can assembled in groups together, see [Notes](http://hl7.org/fhir/R4/observation.html#obsgrouping) below.' |
| Warning | Observation.derivedFrom | Elements differ in definition for mustSupport: 'false' vs 'true' |
| Error | Observation.derivedFrom | Type Mismatch: Reference([CanonicalType[http://hl7.org/fhir/StructureDefinition/DocumentReference], CanonicalType[http://hl7.org/fhir/StructureDefinition/ImagingStudy], CanonicalType[http://hl7.org/fhir/StructureDefinition/Media], CanonicalType[http://hl7.org/fhir/StructureDefinition/QuestionnaireResponse], CanonicalType[http://hl7.org/fhir/StructureDefinition/MolecularSequence], CanonicalType[http://hl7.org/fhir/StructureDefinition/vitalsigns]]) vs Reference([CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-questionnaireresponse], CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-survey]]) |
| Information | StructureDefinition.short | Values for short differ: 'Component observations' vs 'Component results' |
| Information | StructureDefinition.definition | Values for definition differ: 'Used when reporting component observation such as systolic and diastolic blood pressure.' vs 'Some observations have multiple component observations. These component observations are expressed as separate code value pairs that share the same attributes. Examples include systolic and diastolic component observations for blood pressure measurement and multiple component observations for genetics observations.' |
| Information | StructureDefinition.comment | Values for comment differ: 'For a discussion on the ways Observations can be assembled in groups together see [Notes](http://hl7.org/fhir/observation.html#notes) below.' vs 'For a discussion on the ways Observations can be assembled in groups together see [Notes](http://hl7.org/fhir/R4/observation.html#notes) below.' |
| Warning | Observation.component | Elements differ in definition for mustSupport: 'true' vs 'false' |
| Information | Observation.component | Element maximum cardinalities differ: '2147483647' vs '0' |
| Information | StructureDefinition.requirements | Values for requirements differ: 'Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://hl7.org/fhir/extensibility.html#modifierExtension).' vs 'Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://hl7.org/fhir/R4/extensibility.html#modifierExtension).' |
| Warning | Observation.component.code | Elements differ in definition for mustSupport: 'true' vs 'false' |
| Information | StructureDefinition.short | Values for short differ: 'Vital Sign Component Value' vs 'Actual component result' |
| Information | StructureDefinition.definition | Values for definition differ: 'Vital Signs value are typically recorded using the Quantity data type. For supporting observations such as cuff size could use other datatypes such as CodeableConcept.' vs 'The information determined as a result of making the observation, if the information has a simple value.' |
| Information | StructureDefinition.comment | Values for comment differ: 'Used when observation has a set of component observations. An observation may have both a value (e.g. an Apgar score) and component observations (the observations from which the Apgar score was 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 additional guidance, see the [Notes section](http://hl7.org/fhir/observation.html#notes) below.' vs 'Used when observation has a set of component observations. An observation may have both a value (e.g. an Apgar score) and component observations (the observations from which the Apgar score was 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 additional guidance, see the [Notes section](http://hl7.org/fhir/R4/observation.html#notes) below.' |
| Information | StructureDefinition.requirements | Values for requirements differ: '9. SHALL contain exactly one [1..1] value with @xsi:type='PQ' (CONF:7305).' vs 'An observation exists to have a value, though it might not if it is in error, or if it represents a group of observations.' |
| Warning | Observation.component.value[x] | Elements differ in definition for mustSupport: 'true' vs 'false' |
| Warning | Observation.component.dataAbsentReason | Elements differ in definition for mustSupport: 'true' vs 'false' |
| Name | Value | Comments | |
|---|---|---|---|
 abstract | false | ||
| baseDefinition | http://hl7.org/fhir/us/core/StructureDefinition/us-core-vital-signs | http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-survey |
|
| copyright | Used by permission of HL7 International, all rights reserved Creative Commons License |
| |
| date | 2023-10-17 | 2024-01-05T16:57:50+00:00 |
|
| description | To promote interoperability and adoption through common implementation, this profile sets minimum expectations for the Observation resource to record, search, and fetch head circumference observations with a standard LOINC code and UCUM units of measure. It is based on the US Core Vital Signs Profile and identifies which *additional* core elements, extensions, vocabularies, and value sets **SHALL** be present and constrains the way the elements are used when using the profile. It provides the floor for standards development for specific use cases. | A point in time collection of post-acute care observations for a patient. This profile is used for exchanging a set of observation data collected through the use of a structured resource (e.g., assessment tool, instrument, or screen) with multiple questions. |
|
| experimental | false |
| |
| fhirVersion | 4.0.1 | ||
| jurisdiction | |||
 jurisdiction[0] | urn:iso:std:iso:3166#US | ||
| kind | resource | ||
| name | USCoreHeadCircumferenceProfile | PFECollection |
|
| publisher | HL7 International / Cross-Group Projects | HL7 International / Patient Care |
|
| purpose | |||
| status | active | draft |
|
| title | US Core Head Circumference Profile | Personal Functioning and Engagement Collection |
|
| type | Observation | ||
| url | http://hl7.org/fhir/us/core/StructureDefinition/us-core-head-circumference | http://hl7.org/fhir/us/pacio-pfe/StructureDefinition/pfe-collection |
|
| version | 7.0.0-ballot | 1.0.0 |
|
| Name | L Flags | L Card. | L Type | L Description & Constraints | R Flags | R Card. | L Type | L Description & Constraints | Comments | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
 Observation | C | 0..* | USCoreVitalSignsProfile | US Core Head Circumference Profile | C | 0..* | USCoreObservationSurveyProfile | Survey Observation | |||||||||
 id | Σ | 0..1 | id | Logical id of this artifact | Σ | 0..1 | id | Logical id of this artifact | |||||||||
| meta | Σ | 0..1 | Meta | Metadata about the resource | Σ | 0..1 | Meta | Metadata about the resource | |||||||||
| implicitRules | ?!Σ | 0..1 | uri | A set of rules under which this content was created | ?!Σ | 0..1 | uri | A set of rules under which this content was created | |||||||||
| language | 0..1 | code | Language of the resource content Binding: ?? (preferred): A human language.
| 0..1 | code | Language of the resource content Binding: ?? (preferred): A human language.
| |||||||||||
| text | 0..1 | Narrative | Text summary of the resource, for human interpretation | 0..1 | Narrative | Text summary of the resource, for human interpretation | |||||||||||
| contained | 0..* | Resource | Contained, inline Resources | 0..* | Resource | Contained, inline Resources | |||||||||||
 extension | 0..* | Extension | Additional content defined by implementations | 0..* | Extension | Extension Slice: Unordered, Open by value:url | |||||||||||
 modifierExtension | ?! | 0..* | Extension | Extensions that cannot be ignored | ?! | 0..* | Extension | Extensions that cannot be ignored | |||||||||
| identifier | Σ | 0..* | Identifier | Business Identifier for observation | Σ | 0..* | Identifier | Business Identifier for observation | |||||||||
| basedOn | Σ | 0..* | Reference(CarePlan | DeviceRequest | ImmunizationRecommendation | MedicationRequest | NutritionOrder | ServiceRequest) | Fulfills plan, proposal or order | Σ | 0..* | Reference(CarePlan | DeviceRequest | ImmunizationRecommendation | MedicationRequest | NutritionOrder | ServiceRequest) | Fulfills plan, proposal or order | |||||||||
| partOf | Σ | 0..* | Reference(MedicationAdministration | MedicationDispense | MedicationStatement | Procedure | Immunization | ImagingStudy) | Part of referenced event | Σ | 0..* | Reference(MedicationAdministration | MedicationDispense | MedicationStatement | Procedure | Immunization | ImagingStudy) | Part of referenced event | |||||||||
| status | ?!SΣ | 1..1 | code | registered | preliminary | final | amended + Binding: ?? (required) | ?!SΣ | 1..1 | code | Should have the value 'final' when all the observatons are complete and there are no further actions needed. Otherwise, another value from the value set may appropriately be used. Binding: ?? (required): Codes providing the status of an observation. | |||||||||
| Slices for category | S | 1..* | CodeableConcept | Classification of type of observation Slice: Unordered, Open by value:coding.code, value:coding.system Binding: ?? (preferred): Codes for high level observation categories. | S | 2..* | CodeableConcept | Classification of type of observation Slice: Unordered, Open by pattern:$this Binding: ?? (preferred): Codes for high level observation categories. |
| ||||||||
| code | SΣ | 1..1 | CodeableConcept | Head Circumference Binding: ?? (extensible): The vital sign codes from the base FHIR and US Core Vital Signs. Required Pattern: {"coding":[{"system":"http://loinc.org","code":"9843-4"}]} | SΣ | 1..1 | CodeableConcept | For a Post-Acute Care structured assessment resource such as an instrument or screen, use a LOINC code to identify the instrument/screen name or panel/section title to indicate the kind of assessment. Binding: ?? (preferred) | |||||||||
| subject | SΣ | 1..1 | Reference(US Core Patient Profile) | Who and/or what the observation is about | SΣ | 1..1 | Reference(US Core Patient Profile) | Who and/or what the observation is about | |||||||||
| focus | Σ | 0..* | Reference(Resource) | What the observation is about, when it is not about the subject of record | Σ | 0..* | Reference(Resource) | What the observation is about, when it is not about the subject of record | |||||||||
| encounter | Σ | 0..1 | Reference(Encounter) | Healthcare event during which this observation is made | Σ | 0..1 | Reference(Encounter) | Healthcare event during which this observation is made | |||||||||
| effective[x] | SΣC | 1..1 | dateTime S, Period | Often just a dateTime for Vital Signs | SΣC | 1..1 | dateTime S, Period | Clinical relevant time for an assessment such as post-acute care observations performed with structured evaluation tools is the time the evaluation occurs, i.e., when the clinician obtains the answers entered in the tool. However, the only timing available may be when then tool is completed by the clinician. That timing is generally documented as a point in time (dateTime). | |||||||||
| issued | Σ | 0..1 | instant | Date/Time this version was made available | Σ | 0..1 | instant | Date/Time this version was made available | |||||||||
| performer | Σ | 0..* | Reference(Practitioner | PractitionerRole | Organization | CareTeam | Patient | RelatedPerson) | Who is responsible for the observation | SΣ | 1..* | Reference(US Core Practitioner Profile S | US Core PractitionerRole Profile | US Core Organization Profile) | The person who performed the assessment. The preferred way to specify the performer is to use the PractitionerRole resource to provide both the practitioner and organization. |
| ||||||||
| Slices for value[x] | SΣC | 0..1 | Quantity S, CodeableConcept, string, boolean, integer, Range, Ratio, SampledData, time, dateTime, Period | Vital Signs Value Slice: Unordered, Open by type:$this Binding: ?? (extensible): Common UCUM units for recording Vital Signs. | SΣC | 0..0 |
| ||||||||||
| dataAbsentReason | SC | 0..1 | CodeableConcept | Why the result is missing Binding: ?? (extensible): Codes specifying why the result (Observation.value[x]) is missing. | SC | 0..1 | CodeableConcept | Why the result is missing Binding: ?? (extensible): Codes specifying why the result (Observation.value[x]) is missing. | |||||||||
| interpretation | 0..* | CodeableConcept | High, low, normal, etc. Binding: ?? (extensible): Codes identifying interpretations of observations. | 0..* | CodeableConcept | High, low, normal, etc. Binding: ?? (extensible): Codes identifying interpretations of observations. | |||||||||||
| note | 0..* | Annotation | Comments about the observation | 0..* | Annotation | Comments about the observation | |||||||||||
| bodySite | 0..1 | CodeableConcept | Observed body part Binding: ?? (example): Codes describing anatomical locations. May include laterality. | 0..1 | CodeableConcept | Observed body part Binding: ?? (example): Codes describing anatomical locations. May include laterality. | |||||||||||
| method | 0..1 | CodeableConcept | How it was done Binding: ?? (example): Methods for simple observations. | 0..1 | CodeableConcept | How it was done Binding: ?? (example): Methods for simple observations. | |||||||||||
| specimen | 0..1 | Reference(Specimen) | Specimen used for this observation | 0..1 | Reference(Specimen) | Specimen used for this observation | |||||||||||
| device | 0..1 | Reference(Device | DeviceMetric) | (Measurement) Device | 0..1 | Reference(Device | DeviceMetric) | (Measurement) Device | |||||||||||
 referenceRange | C | 0..* | BackboneElement | Provides guide for interpretation | C | 0..* | BackboneElement | Provides guide for interpretation | |||||||||
 id | 0..1 | string | Unique id for inter-element referencing | 0..1 | string | Unique id for inter-element referencing | |||||||||||
| extension | 0..* | Extension | Additional content defined by implementations | 0..* | Extension | Additional content defined by implementations | |||||||||||
| modifierExtension | ?!Σ | 0..* | Extension | Extensions that cannot be ignored even if unrecognized | ?!Σ | 0..* | Extension | Extensions that cannot be ignored even if unrecognized | |||||||||
| low | C | 0..1 | ?? | Low Range, if relevant | C | 0..1 | ?? | Low Range, if relevant | |||||||||
| high | C | 0..1 | ?? | High Range, if relevant | C | 0..1 | ?? | High Range, if relevant | |||||||||
| type | 0..1 | CodeableConcept | Reference range qualifier Binding: ?? (preferred): Code for the meaning of a reference range. | 0..1 | CodeableConcept | Reference range qualifier Binding: ?? (preferred): Code for the meaning of a reference range. | |||||||||||
| appliesTo | 0..* | CodeableConcept | Reference range population Binding: ?? (example): Codes identifying the population the reference range applies to. | 0..* | CodeableConcept | Reference range population Binding: ?? (example): Codes identifying the population the reference range applies to. | |||||||||||
| age | 0..1 | Range | Applicable age range, if relevant | 0..1 | Range | Applicable age range, if relevant | |||||||||||
| text | 0..1 | string | Text based reference range in an observation | 0..1 | string | Text based reference range in an observation | |||||||||||
| hasMember | Σ | 0..* | Reference(QuestionnaireResponse | MolecularSequence | Vital Signs Profile) | Used when reporting vital signs panel components | SΣ | 0..* | Reference(Personal Functioning and Engagement Single Observation) | Each post-acute care observation in the collection. May also be another collection to support nested sections. |
| ||||||||
| derivedFrom | Σ | 0..* | Reference(DocumentReference | ImagingStudy | Media | QuestionnaireResponse | MolecularSequence | Vital Signs Profile) | Related measurements the observation is made from | SΣ | 0..* | Reference(US Core QuestionnaireResponse Profile S | US Core Observation Survey Profile S) | Should point back to the QuestionnaireResponse that this resource is derived from. |
| ||||||||
 component | SΣC | 0..* | BackboneElement | Component observations | Σ | 0..0 |
| ||||||||||
 id | 0..1 | string | Unique id for inter-element referencing | 0..1 | string | Unique id for inter-element referencing | |||||||||||
| extension | 0..* | Extension | Additional content defined by implementations | 0..* | Extension | Additional content defined by implementations | |||||||||||
| modifierExtension | ?!Σ | 0..* | Extension | Extensions that cannot be ignored even if unrecognized | ?!Σ | 0..* | Extension | Extensions that cannot be ignored even if unrecognized | |||||||||
| code | SΣ | 1..1 | CodeableConcept | Type of component observation (code / type) Binding: ?? (extensible): The vital sign codes from the base FHIR and US Core Vital Signs. | Σ | 1..1 | CodeableConcept | Type of component observation (code / type) Binding: ?? (example): Codes identifying names of simple observations. |
| ||||||||
| value[x] | SΣC | 0..1 | Quantity S, CodeableConcept, string, boolean, integer, Range, Ratio, SampledData, time, dateTime, Period | Vital Sign Component Value Binding: ?? (extensible): Common UCUM units for recording Vital Signs. | Σ | 0..1 | Quantity, CodeableConcept, string, boolean, integer, Range, Ratio, SampledData, time, dateTime, Period | Actual component result |
| ||||||||
| dataAbsentReason | SC | 0..1 | CodeableConcept | Why the component result is missing Binding: ?? (extensible): Codes specifying why the result (Observation.value[x]) is missing. | C | 0..1 | CodeableConcept | Why the component result is missing Binding: ?? (extensible): Codes specifying why the result (Observation.value[x]) is missing. |
| ||||||||
| interpretation | 0..* | CodeableConcept | High, low, normal, etc. Binding: ?? (extensible): Codes identifying interpretations of observations. | 0..* | CodeableConcept | High, low, normal, etc. Binding: ?? (extensible): Codes identifying interpretations of observations. | |||||||||||
 referenceRange | 0..* | See referenceRange (Observation) | Provides guide for interpretation of component result | 0..* | See referenceRange (Observation) | Provides guide for interpretation of component result | |||||||||||
| Documentation for this format | |||||||||||||||||