| Left: | US Core Laboratory Result Observation Profile (http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-lab) |
| Right: | PACIO Cognitive Status Collection (http://hl7.org/fhir/us/pacio-cs/StructureDefinition/pacio-csc) |
| Error | StructureDefinition.url | Values for url differ: 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-lab' vs 'http://hl7.org/fhir/us/pacio-cs/StructureDefinition/pacio-csc' |
| Error | StructureDefinition.version | Values for version differ: '7.0.0' vs '1.0.0' |
| Information | StructureDefinition.name | Values for name differ: 'USCoreLaboratoryResultObservationProfile' vs 'CognitiveStatusCollection' |
| Information | StructureDefinition.title | Values for title differ: 'US Core Laboratory Result Observation Profile' vs 'PACIO Cognitive Status Collection' |
| Information | StructureDefinition.date | Values for date differ: '2023-10-17' vs '2024-11-05T07:56:05+00:00' |
| Information | StructureDefinition.publisher | Values for publisher differ: 'HL7 International / Cross-Group Projects' vs 'HL7 Patient Care Work Group' |
| Error | StructureDefinition.baseDefinition | Values for baseDefinition differ: 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-clinical-result' vs 'http://hl7.org/fhir/StructureDefinition/Observation' |
| Warning | Observation.meta | Elements differ in definition for mustSupport: 'true' vs 'false' |
| 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.short | Values for short differ: 'Fulfills plan, proposal or order' vs 'Currently not used in CognitiveStatusCollection.' |
| Information | StructureDefinition.short | Values for short differ: 'Part of referenced event' vs 'Currently not used in CognitiveStatusCollection.' |
| 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.' |
| Warning | Observation.status | Elements differ in definition for mustSupport: 'true' vs 'false' |
| Information | StructureDefinition.short | Values for short differ: 'Classification of type of observation' vs 'A second category code may be used along with the code “functioning”. For example, for assessment tool/survey instrument observations use “survey” as a second code.' |
| Warning | Observation.category | Elements differ in definition for mustSupport: 'true' vs 'false' |
| Information | StructureDefinition.short | Values for short differ: 'Laboratory Test Name' 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: 'The name of the clinical test or procedure performed on a patient. A LOINC **SHALL** be used if the concept is present in LOINC.' vs 'Describes what was observed. Sometimes this is called the observation 'name'.' |
| Information | StructureDefinition.comment | Values for comment differ: 'The typical patterns for codes are: 1) a LOINC code either as a translation from a 'local' code or as a primary code, or 2) a local code only if no suitable LOINC exists, or 3) both the local and the LOINC translation. Systems SHALL be capable of sending the local code if one exists. When using LOINC , Use either the SHORTNAME or LONG_COMMON_NAME field for the display.' vs '*All* code-value and, if present, component.code-component.value pairs need to be taken into account to correctly understand the meaning of the observation.' |
| Warning | Observation.code | Elements differ in definition for mustSupport: 'true' vs 'false' |
| Information | StructureDefinition.short | Values for short differ: 'Who and/or what the observation is about' vs 'Should only reference a Patient resource.' |
| Warning | Observation.subject | Elements differ in definition for mustSupport: 'true' vs 'false' |
| Information | StructureDefinition.short | Values for short differ: 'What the observation is about, when it is not about the subject of record' vs 'Currently not used in CognitiveStatusCollection.' |
| Information | StructureDefinition.short | Values for short differ: 'Encounter associated with Observation' vs 'Healthcare event during which this observation is made' |
| Warning | Observation.encounter | Elements differ in definition for mustSupport: 'true' vs 'false' |
| Information | StructureDefinition.short | Values for short differ: 'Clinically relevant time/time-period for observation' vs 'Clinical relevant time for an assessment such as cognitive assessments 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: '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.' vs 'Clinical relevant time for an assessment such as cognitive assessments 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/R4/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).' |
| Warning | Observation.effective[x] | Elements differ in definition for mustSupport: 'true' vs 'false' |
| Information | Observation.effective[x] | Element minimum cardinalities differ: '0' vs '1' |
| Information | StructureDefinition.short | Values for short differ: 'Date/Time this version was made available' vs 'Currently not used in CognitiveStatusCollection.' |
| 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.' |
| Information | Observation.performer | Element minimum cardinalities differ: '0' vs '1' |
| Information | StructureDefinition.short | Values for short differ: 'Result Value' vs 'If used, should use the CodeableConcept datatype whenever possible to provide a suitable code to define the concept for the observation data. When capturing a collection of related observations, typically this field is not used. If the outcome of an assessment includes one or more summary scores, leave this field unused and use the 'hasMember' field to point to one or more Observation resources with each of which has a score provided in the 'value' field.' |
| Information | StructureDefinition.definition | Values for definition differ: 'The Laboratory result value. If a coded value, the valueCodeableConcept.code **SHOULD** be selected from [SNOMED CT](http://hl7.org/fhir/ValueSet/uslab-obs-codedresults) if the concept exists. If a numeric value, valueQuantity.code **SHALL** be selected from [UCUM](http://unitsofmeasure.org). A FHIR [UCUM Codes value set](http://hl7.org/fhir/STU3/valueset-ucum-units.html) that defines all UCUM codes is in the FHIR specification.' vs 'The information determined as a result of making the observation, if the information has a simple value.' |
| Warning | Observation.value[x] | Elements differ in definition for mustSupport: 'true' vs 'false' |
| Information | StructureDefinition.short | Values for short differ: 'Why the result is missing' vs 'Currently not used in CognitiveStatusCollection.' |
| Warning | Observation.dataAbsentReason | Elements differ in definition for mustSupport: 'true' vs 'false' |
| Information | StructureDefinition.short | Values for short differ: 'Result interpretation' vs 'Currently not used in CognitiveStatusCollection.' |
| Information | StructureDefinition.comment | Values for comment differ: 'Categorical assessment of a laboratory value, often in relation to a test's reference range. Examples include but are not limited to high, low, critical, and normal.' vs 'Historically used for laboratory results (known as 'abnormal flag' ), its use extends to other use cases where coded interpretations are relevant. Often reported as one or more simple compact codes this element is often placed adjacent to the result value in reports and flow sheets to signal the meaning/normalcy status of the result.' |
| Warning | Observation.interpretation | Elements differ in definition for mustSupport: 'true' vs 'false' |
| Information | StructureDefinition.short | Values for short differ: 'Observed body part' vs 'Currently not used in CognitiveStatusCollection.' |
| Information | StructureDefinition.short | Values for short differ: 'How it was done' vs 'Currently not used in CognitiveStatusCollection.' |
| Information | StructureDefinition.short | Values for short differ: 'Specimen used for this observation' vs 'Currently not used in CognitiveStatusCollection.' |
| Warning | Observation.specimen | Elements differ in definition for mustSupport: 'true' vs 'false' |
| Information | StructureDefinition.short | Values for short differ: '(Measurement) Device' vs 'Currently not used in CognitiveStatusCollection.' |
| Information | StructureDefinition.short | Values for short differ: 'Result reference range' vs 'Currently not used in CognitiveStatusCollection.' |
| Information | StructureDefinition.comment | Values for comment differ: 'Upper and lower limit of test values expected for a designated population of individuals. Reference range values may differ by patient characteristics, laboratory test manufacturer and laboratory test performer.' vs '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 might 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.' |
| Warning | Observation.referenceRange | Elements differ in definition for mustSupport: 'true' vs 'false' |
| Information | StructureDefinition.short | Values for short differ: 'Related resource that belongs to the Observation group' vs 'Each cognitive status observation in the collection.' |
| 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/R4/observation.html#obsgrouping) below. Note that a system may calculate results from [QuestionnaireResponse](questionnaireresponse.html) into a final score and represent the score as an Observation.' vs '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/R4/observation.html#obsgrouping) below. Note that a system may calculate results from [QuestionnaireResponse](http://hl7.org/fhir/R4/questionnaireresponse.html) into a final score and represent the score as an Observation.' |
| Warning | Observation.hasMember | Elements differ in definition for mustSupport: 'false' vs 'true' |
| Information | StructureDefinition.short | Values for short differ: 'Related measurements the observation is made from' vs 'Should point back to the SDC QuestionnaireResponse that this resource is derived from.' |
| 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/Observation], CanonicalType[http://hl7.org/fhir/StructureDefinition/MolecularSequence]]) vs Reference([CanonicalType[http://hl7.org/fhir/uv/sdc/StructureDefinition/sdc-questionnaireresponse]]) |
| Information | StructureDefinition.short | Values for short differ: 'Component results' vs 'Currently not used in CognitiveStatusCollection.' |
| Name | Value | Comments | |
|---|---|---|---|
 abstract | false | ||
| baseDefinition | http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-clinical-result | http://hl7.org/fhir/StructureDefinition/Observation |
|
| copyright | Used by permission of HL7 International, all rights reserved Creative Commons License |
| |
| date | 2023-10-17 | 2024-11-05T07:56:05+00:00 |
|
| description | The US Core Laboratory Result Observation Profile is based upon the US Core Observation Clinical Result Profile and, along with the US Core DiagnosticReport Profile for Laboratory Results Reporting, meets the U.S. Core Data for Interoperability (USCDI) Laboratory requirements. Laboratory results are grouped and summarized using the DiagnosticReport resource, which references Observation resources. Each Observation resource represents an individual laboratory test and result value, a “nested” panel (such as a microbial susceptibility panel) that references other observations, or rarely a laboratory test with component result values. The US Core Laboratory Result Observation Profile sets minimum expectations for the Observation resource to record, search, and fetch laboratory test results associated with a patient to promote interoperability and adoption through common implementation. It identifies which core elements, extensions, vocabularies, and value sets SHALL be present in the resource and constrains the way the elements are used when using this profile. It provides the floor for standards development for specific use cases. | A point in time collection of cognitive status 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). |
|
| experimental | false |
| |
| fhirVersion | 4.0.1 | ||
| jurisdiction | |||
 jurisdiction[0] | urn:iso:std:iso:3166#US | ||
| kind | resource | ||
| name | USCoreLaboratoryResultObservationProfile | CognitiveStatusCollection |
|
| publisher | HL7 International / Cross-Group Projects | HL7 Patient Care Work Group |
|
| purpose | |||
| status | active | ||
| title | US Core Laboratory Result Observation Profile | PACIO Cognitive Status Collection |
|
| type | Observation | ||
| url | http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-lab | http://hl7.org/fhir/us/pacio-cs/StructureDefinition/pacio-csc |
|
| version | 7.0.0 | 1.0.0 |
|
| Name | L Flags | L Card. | L Type | L Description & Constraints | R Flags | R Card. | R Type | R Description & Constraints | Comments | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
 Observation | C | 0..* | USCoreObservationClinicalResultProfile | Measurements and simple assertions obs-6: dataAbsentReason SHALL only be present if Observation.value[x] is not present obs-7: If Observation.code is the same as an Observation.component.code then the value element associated with the code SHALL NOT be present us-core-2: If there is no component or hasMember element then either a value[x] or a data absent reason must be present | C | 0..* | Observation | Measurements and simple assertions obs-6: dataAbsentReason SHALL only be present if Observation.value[x] is not present obs-7: If Observation.code is the same as an Observation.component.code then the value element associated with the code SHALL NOT be present | |||||||||
 id | Σ | 0..1 | id | Logical id of this artifact | Σ | 0..1 | id | Logical id of this artifact | |||||||||
 meta | SΣ | 0..1 | Meta | Metadata about the resource | Σ | 0..1 | Meta | Metadata about the resource |
| ||||||||
 id | 0..1 | string | Unique id for inter-element referencing |
| |||||||||||||
 Slices for extension | 0..* | Extension | Additional content defined by implementations Slice: Unordered, Open by value:url |
| |||||||||||||
| versionId | Σ | 0..1 | id | Version specific identifier |
| ||||||||||||
| lastUpdated | SΣ | 0..1 | instant | When the resource last changed |
| ||||||||||||
| source | Σ | 0..1 | uri | Identifies where the resource comes from |
| ||||||||||||
| profile | Σ | 0..* | canonical(StructureDefinition) | Profiles this resource claims to conform to |
| ||||||||||||
| security | Σ | 0..* | Coding | Security Labels applied to this resource Binding: ?? (extensible): Security Labels from the Healthcare Privacy and Security Classification System. |
| ||||||||||||
| tag | Σ | 0..* | Coding | Tags applied to this resource Binding: ?? (example): Codes that represent various types of tags, commonly workflow-related; e.g. "Needs review by Dr. Jones". |
| ||||||||||||
| 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) | Currently not used in CognitiveStatusCollection. | |||||||||
| partOf | Σ | 0..* | Reference(MedicationAdministration | MedicationDispense | MedicationStatement | Procedure | Immunization | ImagingStudy) | Part of referenced event | Σ | 0..* | Reference(MedicationAdministration | MedicationDispense | MedicationStatement | Procedure | Immunization | ImagingStudy) | Currently not used in CognitiveStatusCollection. | |||||||||
| status | ?!SΣ | 1..1 | code | registered | preliminary | final | amended + Binding: ?? (required): Codes providing the status of an observation. | ?!Σ | 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 pattern:$this Binding: ?? (preferred): Codes for high level observation categories. | 1..* | CodeableConcept | A second category code may be used along with the code “functioning”. For example, for assessment tool/survey instrument observations use “survey” as a second code. Slice: Unordered, Open by pattern:coding Binding: ?? (preferred): Codes for high level observation categories. |
| |||||||||
| code | SΣ | 1..1 | CodeableConcept | Laboratory Test Name Binding: ?? (extensible): Laboratory LOINC Codes | Σ | 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: ?? (extensible) |
| ||||||||
| subject | SΣ | 1..1 | Reference(US Core Patient Profile S | Group | Device | US Core Location Profile) | Who and/or what the observation is about | Σ | 1..1 | Reference(US Core Patient Profile) | Should only reference a Patient resource. |
| ||||||||
| focus | Σ | 0..* | Reference(Resource) | What the observation is about, when it is not about the subject of record | Σ | 0..* | Reference(Resource) | Currently not used in CognitiveStatusCollection. | |||||||||
| encounter | SΣ | 0..1 | Reference(US Core Encounter Profile) | Encounter associated with Observation | Σ | 0..1 | Reference(US Core Encounter Profile) | Healthcare event during which this observation is made |
| ||||||||
| effective[x] | SΣC | 0..1 | dateTime S, Period, Timing, instant | Clinically relevant time/time-period for observation us-core-1: Datetime must be at least to day. | Σ | 1..1 | dateTime, Period | Clinical relevant time for an assessment such as cognitive assessments 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 | Currently not used in CognitiveStatusCollection. | |||||||||
| performer | Σ | 0..* | Reference(Practitioner | PractitionerRole | Organization | CareTeam | Patient | RelatedPerson) | Who is responsible for the observation | Σ | 1..* | Reference(US Core Practitioner Profile | 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. |
| ||||||||
| value[x] | SΣC | 0..1 | Quantity S, CodeableConcept S, string S, boolean, integer, Range, Ratio, SampledData, time, dateTime, Period | Result Value us-core-3: SHALL use UCUM for coded quantity units. us-core-4: SHOULD use Snomed CT for coded Results | ΣC | 0..1 | Quantity, CodeableConcept, string, boolean, integer, Range, Ratio, SampledData, time, dateTime, Period | If used, should use the CodeableConcept datatype whenever possible to provide a suitable code to define the concept for the observation data. When capturing a collection of related observations, typically this field is not used. If the outcome of an assessment includes one or more summary scores, leave this field unused and use the 'hasMember' field to point to one or more Observation resources with each of which has a score provided in the 'value' field. |
| ||||||||
| dataAbsentReason | SC | 0..1 | CodeableConcept | Why the result is missing Binding: ?? (extensible): Codes specifying why the result (Observation.value[x]) is missing. | C | 0..1 | CodeableConcept | Currently not used in CognitiveStatusCollection. Binding: ?? (extensible): Codes specifying why the result (Observation.value[x]) is missing. |
| ||||||||
| interpretation | S | 0..* | CodeableConcept | Result interpretation Binding: ?? (extensible): Observation Interpretation Codes | 0..* | CodeableConcept | Currently not used in CognitiveStatusCollection. 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 | Currently not used in CognitiveStatusCollection. 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 | Currently not used in CognitiveStatusCollection. Binding: ?? (example): Methods for simple observations. | |||||||||||
| specimen | S | 0..1 | Reference(US Core Specimen Profile) | Specimen used for this observation | 0..1 | Reference(Specimen) | Currently not used in CognitiveStatusCollection. |
| |||||||||
| device | 0..1 | Reference(Device | DeviceMetric) | (Measurement) Device | 0..1 | Reference(Device | DeviceMetric) | Currently not used in CognitiveStatusCollection. | |||||||||||
| referenceRange | SC | 0..* | BackboneElement | Result reference range obs-3: Must have at least a low or a high or text us-core-22: SHALL use UCUM for coded quantity units. | C | 0..* | BackboneElement | Currently not used in CognitiveStatusCollection. obs-3: Must have at least a low or a high or text |
| ||||||||
| 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(Observation | QuestionnaireResponse | MolecularSequence) | Related resource that belongs to the Observation group | SΣ | 0..* | Reference(PACIO Cognitive Status) | Each cognitive status observation in the collection. |
| ||||||||
| derivedFrom | Σ | 0..* | Reference(DocumentReference | ImagingStudy | Media | QuestionnaireResponse | Observation | MolecularSequence) | Related measurements the observation is made from | SΣ | 0..* | Reference(SDC Questionnaire Response) | Should point back to the SDC QuestionnaireResponse that this resource is derived from. |
| ||||||||
 component | Σ | 0..* | BackboneElement | Component results | Σ | 0..* | BackboneElement | Currently not used in CognitiveStatusCollection. | |||||||||
 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 | Σ | 1..1 | CodeableConcept | Type of component observation (code / type) Binding: ?? (example): Codes identifying names of simple observations. | Σ | 1..1 | CodeableConcept | Type of component observation (code / type) Binding: ?? (example): Codes identifying names of simple observations. | |||||||||
| value[x] | Σ | 0..1 | Quantity, CodeableConcept, string, boolean, integer, Range, Ratio, SampledData, time, dateTime, Period | Actual component result | Σ | 0..1 | Quantity, CodeableConcept, string, boolean, integer, Range, Ratio, SampledData, time, dateTime, Period | Actual component result | |||||||||
| dataAbsentReason | C | 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 | |||||||||||||||||