PACIO Functional Status Implementation Guide
0.1.0 - CI Build

PACIO Functional Status Implementation Guide - Local Development build (v0.1.0). See the Directory of published versions

Resource Profile: PACIO Functional Status Collection

Defining URL:http://paciowg.github.io/functional-status-ig/StructureDefinition/pacio-fsc
Version:0.1.0
Name:FunctionalStatusCollection
Title:PACIO Functional Status Collection
Status:Active as of 2021-09-23T10:50:45-07:00
Definition:

A point in time collection of functional 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).

Source Resource:XML / JSON / Turtle

The official URL for this profile is: 

http://paciowg.github.io/functional-status-ig/StructureDefinition/pacio-fsc

Formal Views of Profile Content

Description of Profiles, Differentials, Snapshots and how the different presentations work.

This structure is derived from Observation

NameFlagsCard.TypeDescription & Constraintsdoco
.. Observation 0..*ObservationMeasurements and simple assertions
... Slices for extension 0..*ExtensionExtension
Slice: Unordered, Open by value:url
... event-location S0..1Reference(US Core Location Profile)An extension to indicate where the observation event occurred.
URL: http://paciowg.github.io/functional-status-ig/StructureDefinition/event-location
... device-patient-used S0..*Reference(Use of Device)An extension to indicate a record of assistive device usage by a patient during an assessment.
URL: http://paciowg.github.io/functional-status-ig/StructureDefinition/device-patient-used
... partOf 0..*Reference(MedicationAdministration | MedicationDispense | MedicationStatement | Procedure | Immunization | ImagingStudy)Currently not used in FunctionalStatusCollection.
... status 1..1codeShould 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.
... Slices for category 1..*CodeableConceptA 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
.... category:functioning 1..1CodeableConceptClassification of type of observation
Binding: PACIO Functioning Category Value Set (extensible)
..... coding 1..*CodingCode defined by a terminology system
Required Pattern: At least the following
...... system1..1uriIdentity of the terminology system
Fixed Value: http://paciowg.github.io/functional-status-ig/CodeSystem/pacio-cat-cs
...... code1..1codeSymbol in syntax defined by the system
Fixed Value: functioning
...... display1..1stringRepresentation defined by the system
Fixed Value: Functioning
... code 1..1CodeableConceptFor 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: LOINCCodes (extensible)
... subject 1..1Reference(US Core Patient Profile)Should only reference a Patient resource.
... focus 0..*Reference(Resource)Currently not used in FunctionalStatusCollection.
... encounter 0..1Reference(US Core Encounter Profile)Healthcare event during which this observation is made
... effective[x] 1..1Clinical relevant time for an assessment such as functional 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).
.... effectiveDateTimedateTime
.... effectivePeriodPeriod
... issued 0..1instantCurrently not used in FunctionalStatusCollection.
... performer 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] 0..1Quantity, CodeableConcept, string, boolean, integer, Range, Ratio, SampledData, time, dateTime, PeriodIf 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 0..1CodeableConceptCurrently not used in FunctionalStatusCollection.
... interpretation 0..*CodeableConceptCurrently not used in FunctionalStatusCollection.
... bodySite 0..1CodeableConceptCurrently not used in FunctionalStatusCollection.
... method 0..1CodeableConceptCurrently not used in FunctionalStatusCollection.
... specimen 0..1Reference(Specimen)Currently not used in FunctionalStatusCollection.
... device 0..1Reference(Device | DeviceMetric)Currently not used in FunctionalStatusCollection.
... referenceRange 0..*BackboneElementCurrently not used in FunctionalStatusCollection.
... hasMember S0..*Reference(PACIO Functional Status)Each functional status observation in the collection.
... derivedFrom S0..*Reference(QuestionnaireResponse)Should point back to the QuestionnaireResponse that this resource is derived from.
... component 0..*BackboneElementCurrently not used in FunctionalStatusCollection.

doco Documentation for this format
NameFlagsCard.TypeDescription & Constraintsdoco
.. Observation I0..*ObservationMeasurements and simple assertions
... id Σ0..1stringLogical id of this artifact
... meta Σ0..1MetaMetadata about the resource
... implicitRules ?!Σ0..1uriA set of rules under which this content was created
... language 0..1codeLanguage of the resource content
Binding: CommonLanguages (preferred)
Max Binding: AllLanguages: A human language.

... text 0..1NarrativeText summary of the resource, for human interpretation
... contained 0..*ResourceContained, inline Resources
... Slices for extension 0..*ExtensionExtension
Slice: Unordered, Open by value:url
... event-location S0..1Reference(US Core Location Profile)An extension to indicate where the observation event occurred.
URL: http://paciowg.github.io/functional-status-ig/StructureDefinition/event-location
... device-patient-used S0..*Reference(Use of Device)An extension to indicate a record of assistive device usage by a patient during an assessment.
URL: http://paciowg.github.io/functional-status-ig/StructureDefinition/device-patient-used
... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
... identifier Σ0..*IdentifierBusiness Identifier for observation
... basedOn Σ0..*Reference(CarePlan | DeviceRequest | ImmunizationRecommendation | MedicationRequest | NutritionOrder | ServiceRequest)Currently not used in FunctionalStatusCollection.
... partOf Σ0..*Reference(MedicationAdministration | MedicationDispense | MedicationStatement | Procedure | Immunization | ImagingStudy)Currently not used in FunctionalStatusCollection.
... status ?!Σ1..1codeShould 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: ObservationStatus (required): Codes providing the status of an observation.

... Slices for category 1..*CodeableConceptA 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: ObservationCategoryCodes (preferred): Codes for high level observation categories.


.... category:functioning 1..1CodeableConceptClassification of type of observation
Binding: PACIO Functioning Category Value Set (extensible)
..... id 0..1stringUnique id for inter-element referencing
..... Slices for extension 0..*ExtensionAdditional content defined by implementations
Slice: Unordered, Open by value:url
..... coding Σ1..*CodingCode defined by a terminology system

Required Pattern: At least the following
...... id0..1stringUnique id for inter-element referencing
...... extension0..*ExtensionAdditional content defined by implementations
...... system1..1uriIdentity of the terminology system
Fixed Value: http://paciowg.github.io/functional-status-ig/CodeSystem/pacio-cat-cs
...... version0..1stringVersion of the system - if relevant
...... code1..1codeSymbol in syntax defined by the system
Fixed Value: functioning
...... display1..1stringRepresentation defined by the system
Fixed Value: Functioning
...... userSelected0..1booleanIf this coding was chosen directly by the user
..... text Σ0..1stringPlain text representation of the concept
... code Σ1..1CodeableConceptFor 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: LOINCCodes (extensible)
... subject Σ1..1Reference(US Core Patient Profile)Should only reference a Patient resource.
... focus Σ0..*Reference(Resource)Currently not used in FunctionalStatusCollection.
... encounter Σ0..1Reference(US Core Encounter Profile)Healthcare event during which this observation is made
... effective[x] Σ1..1Clinical relevant time for an assessment such as functional 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).
.... effectiveDateTimedateTime
.... effectivePeriodPeriod
... issued Σ0..1instantCurrently not used in FunctionalStatusCollection.
... performer Σ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] ΣI0..1If 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.
.... valueQuantityQuantity
.... valueCodeableConceptCodeableConcept
.... valueStringstring
.... valueBooleanboolean
.... valueIntegerinteger
.... valueRangeRange
.... valueRatioRatio
.... valueSampledDataSampledData
.... valueTimetime
.... valueDateTimedateTime
.... valuePeriodPeriod
... dataAbsentReason I0..1CodeableConceptCurrently not used in FunctionalStatusCollection.
Binding: DataAbsentReason (extensible): Codes specifying why the result (Observation.value[x]) is missing.

... interpretation 0..*CodeableConceptCurrently not used in FunctionalStatusCollection.
Binding: ObservationInterpretationCodes (extensible): Codes identifying interpretations of observations.


... note 0..*AnnotationComments about the observation
... bodySite 0..1CodeableConceptCurrently not used in FunctionalStatusCollection.
Binding: SNOMEDCTBodyStructures (example): Codes describing anatomical locations. May include laterality.

... method 0..1CodeableConceptCurrently not used in FunctionalStatusCollection.
Binding: ObservationMethods (example): Methods for simple observations.

... specimen 0..1Reference(Specimen)Currently not used in FunctionalStatusCollection.
... device 0..1Reference(Device | DeviceMetric)Currently not used in FunctionalStatusCollection.
... referenceRange I0..*BackboneElementCurrently not used in FunctionalStatusCollection.
.... id 0..1stringUnique id for inter-element referencing
.... extension 0..*ExtensionAdditional content defined by implementations
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... low I0..1SimpleQuantityLow Range, if relevant
.... high I0..1SimpleQuantityHigh Range, if relevant
.... type 0..1CodeableConceptReference range qualifier
Binding: ObservationReferenceRangeMeaningCodes (preferred): Code for the meaning of a reference range.

.... appliesTo 0..*CodeableConceptReference range population
Binding: ObservationReferenceRangeAppliesToCodes (example): Codes identifying the population the reference range applies to.


.... age 0..1RangeApplicable age range, if relevant
.... text 0..1stringText based reference range in an observation
... hasMember SΣ0..*Reference(PACIO Functional Status)Each functional status observation in the collection.
... derivedFrom SΣ0..*Reference(QuestionnaireResponse)Should point back to the QuestionnaireResponse that this resource is derived from.
... component Σ0..*BackboneElementCurrently not used in FunctionalStatusCollection.
.... id 0..1stringUnique id for inter-element referencing
.... extension 0..*ExtensionAdditional content defined by implementations
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... code Σ1..1CodeableConceptType of component observation (code / type)
Binding: LOINCCodes (example): Codes identifying names of simple observations.

.... value[x] Σ0..1Actual component result
..... valueQuantityQuantity
..... valueCodeableConceptCodeableConcept
..... valueStringstring
..... valueBooleanboolean
..... valueIntegerinteger
..... valueRangeRange
..... valueRatioRatio
..... valueSampledDataSampledData
..... valueTimetime
..... valueDateTimedateTime
..... valuePeriodPeriod
.... dataAbsentReason I0..1CodeableConceptWhy the component result is missing
Binding: DataAbsentReason (extensible): Codes specifying why the result (Observation.value[x]) is missing.

.... interpretation 0..*CodeableConceptHigh, low, normal, etc.
Binding: ObservationInterpretationCodes (extensible): Codes identifying interpretations of observations.


.... referenceRange 0..*See referenceRange (Observation)Provides guide for interpretation of component result

doco Documentation for this format
NameFlagsCard.TypeDescription & Constraintsdoco
.. Observation I0..*ObservationMeasurements and simple assertions
... event-location 0..1Reference(US Core Location Profile)An extension to indicate where the observation event occurred.
URL: http://paciowg.github.io/functional-status-ig/StructureDefinition/event-location
... device-patient-used 0..*Reference(Use of Device)An extension to indicate a record of assistive device usage by a patient during an assessment.
URL: http://paciowg.github.io/functional-status-ig/StructureDefinition/device-patient-used
... hasMember Σ0..*Reference(PACIO Functional Status)Each functional status observation in the collection.

doco Documentation for this format

Differential View

This structure is derived from Observation

NameFlagsCard.TypeDescription & Constraintsdoco
.. Observation 0..*ObservationMeasurements and simple assertions
... Slices for extension 0..*ExtensionExtension
Slice: Unordered, Open by value:url
... event-location S0..1Reference(US Core Location Profile)An extension to indicate where the observation event occurred.
URL: http://paciowg.github.io/functional-status-ig/StructureDefinition/event-location
... device-patient-used S0..*Reference(Use of Device)An extension to indicate a record of assistive device usage by a patient during an assessment.
URL: http://paciowg.github.io/functional-status-ig/StructureDefinition/device-patient-used
... partOf 0..*Reference(MedicationAdministration | MedicationDispense | MedicationStatement | Procedure | Immunization | ImagingStudy)Currently not used in FunctionalStatusCollection.
... status 1..1codeShould 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.
... Slices for category 1..*CodeableConceptA 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
.... category:functioning 1..1CodeableConceptClassification of type of observation
Binding: PACIO Functioning Category Value Set (extensible)
..... coding 1..*CodingCode defined by a terminology system
Required Pattern: At least the following
...... system1..1uriIdentity of the terminology system
Fixed Value: http://paciowg.github.io/functional-status-ig/CodeSystem/pacio-cat-cs
...... code1..1codeSymbol in syntax defined by the system
Fixed Value: functioning
...... display1..1stringRepresentation defined by the system
Fixed Value: Functioning
... code 1..1CodeableConceptFor 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: LOINCCodes (extensible)
... subject 1..1Reference(US Core Patient Profile)Should only reference a Patient resource.
... focus 0..*Reference(Resource)Currently not used in FunctionalStatusCollection.
... encounter 0..1Reference(US Core Encounter Profile)Healthcare event during which this observation is made
... effective[x] 1..1Clinical relevant time for an assessment such as functional 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).
.... effectiveDateTimedateTime
.... effectivePeriodPeriod
... issued 0..1instantCurrently not used in FunctionalStatusCollection.
... performer 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] 0..1Quantity, CodeableConcept, string, boolean, integer, Range, Ratio, SampledData, time, dateTime, PeriodIf 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 0..1CodeableConceptCurrently not used in FunctionalStatusCollection.
... interpretation 0..*CodeableConceptCurrently not used in FunctionalStatusCollection.
... bodySite 0..1CodeableConceptCurrently not used in FunctionalStatusCollection.
... method 0..1CodeableConceptCurrently not used in FunctionalStatusCollection.
... specimen 0..1Reference(Specimen)Currently not used in FunctionalStatusCollection.
... device 0..1Reference(Device | DeviceMetric)Currently not used in FunctionalStatusCollection.
... referenceRange 0..*BackboneElementCurrently not used in FunctionalStatusCollection.
... hasMember S0..*Reference(PACIO Functional Status)Each functional status observation in the collection.
... derivedFrom S0..*Reference(QuestionnaireResponse)Should point back to the QuestionnaireResponse that this resource is derived from.
... component 0..*BackboneElementCurrently not used in FunctionalStatusCollection.

doco Documentation for this format

Snapshot View

NameFlagsCard.TypeDescription & Constraintsdoco
.. Observation I0..*ObservationMeasurements and simple assertions
... id Σ0..1stringLogical id of this artifact
... meta Σ0..1MetaMetadata about the resource
... implicitRules ?!Σ0..1uriA set of rules under which this content was created
... language 0..1codeLanguage of the resource content
Binding: CommonLanguages (preferred)
Max Binding: AllLanguages: A human language.

... text 0..1NarrativeText summary of the resource, for human interpretation
... contained 0..*ResourceContained, inline Resources
... Slices for extension 0..*ExtensionExtension
Slice: Unordered, Open by value:url
... event-location S0..1Reference(US Core Location Profile)An extension to indicate where the observation event occurred.
URL: http://paciowg.github.io/functional-status-ig/StructureDefinition/event-location
... device-patient-used S0..*Reference(Use of Device)An extension to indicate a record of assistive device usage by a patient during an assessment.
URL: http://paciowg.github.io/functional-status-ig/StructureDefinition/device-patient-used
... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
... identifier Σ0..*IdentifierBusiness Identifier for observation
... basedOn Σ0..*Reference(CarePlan | DeviceRequest | ImmunizationRecommendation | MedicationRequest | NutritionOrder | ServiceRequest)Currently not used in FunctionalStatusCollection.
... partOf Σ0..*Reference(MedicationAdministration | MedicationDispense | MedicationStatement | Procedure | Immunization | ImagingStudy)Currently not used in FunctionalStatusCollection.
... status ?!Σ1..1codeShould 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: ObservationStatus (required): Codes providing the status of an observation.

... Slices for category 1..*CodeableConceptA 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: ObservationCategoryCodes (preferred): Codes for high level observation categories.


.... category:functioning 1..1CodeableConceptClassification of type of observation
Binding: PACIO Functioning Category Value Set (extensible)
..... id 0..1stringUnique id for inter-element referencing
..... Slices for extension 0..*ExtensionAdditional content defined by implementations
Slice: Unordered, Open by value:url
..... coding Σ1..*CodingCode defined by a terminology system

Required Pattern: At least the following
...... id0..1stringUnique id for inter-element referencing
...... extension0..*ExtensionAdditional content defined by implementations
...... system1..1uriIdentity of the terminology system
Fixed Value: http://paciowg.github.io/functional-status-ig/CodeSystem/pacio-cat-cs
...... version0..1stringVersion of the system - if relevant
...... code1..1codeSymbol in syntax defined by the system
Fixed Value: functioning
...... display1..1stringRepresentation defined by the system
Fixed Value: Functioning
...... userSelected0..1booleanIf this coding was chosen directly by the user
..... text Σ0..1stringPlain text representation of the concept
... code Σ1..1CodeableConceptFor 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: LOINCCodes (extensible)
... subject Σ1..1Reference(US Core Patient Profile)Should only reference a Patient resource.
... focus Σ0..*Reference(Resource)Currently not used in FunctionalStatusCollection.
... encounter Σ0..1Reference(US Core Encounter Profile)Healthcare event during which this observation is made
... effective[x] Σ1..1Clinical relevant time for an assessment such as functional 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).
.... effectiveDateTimedateTime
.... effectivePeriodPeriod
... issued Σ0..1instantCurrently not used in FunctionalStatusCollection.
... performer Σ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] ΣI0..1If 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.
.... valueQuantityQuantity
.... valueCodeableConceptCodeableConcept
.... valueStringstring
.... valueBooleanboolean
.... valueIntegerinteger
.... valueRangeRange
.... valueRatioRatio
.... valueSampledDataSampledData
.... valueTimetime
.... valueDateTimedateTime
.... valuePeriodPeriod
... dataAbsentReason I0..1CodeableConceptCurrently not used in FunctionalStatusCollection.
Binding: DataAbsentReason (extensible): Codes specifying why the result (Observation.value[x]) is missing.

... interpretation 0..*CodeableConceptCurrently not used in FunctionalStatusCollection.
Binding: ObservationInterpretationCodes (extensible): Codes identifying interpretations of observations.


... note 0..*AnnotationComments about the observation
... bodySite 0..1CodeableConceptCurrently not used in FunctionalStatusCollection.
Binding: SNOMEDCTBodyStructures (example): Codes describing anatomical locations. May include laterality.

... method 0..1CodeableConceptCurrently not used in FunctionalStatusCollection.
Binding: ObservationMethods (example): Methods for simple observations.

... specimen 0..1Reference(Specimen)Currently not used in FunctionalStatusCollection.
... device 0..1Reference(Device | DeviceMetric)Currently not used in FunctionalStatusCollection.
... referenceRange I0..*BackboneElementCurrently not used in FunctionalStatusCollection.
.... id 0..1stringUnique id for inter-element referencing
.... extension 0..*ExtensionAdditional content defined by implementations
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... low I0..1SimpleQuantityLow Range, if relevant
.... high I0..1SimpleQuantityHigh Range, if relevant
.... type 0..1CodeableConceptReference range qualifier
Binding: ObservationReferenceRangeMeaningCodes (preferred): Code for the meaning of a reference range.

.... appliesTo 0..*CodeableConceptReference range population
Binding: ObservationReferenceRangeAppliesToCodes (example): Codes identifying the population the reference range applies to.


.... age 0..1RangeApplicable age range, if relevant
.... text 0..1stringText based reference range in an observation
... hasMember SΣ0..*Reference(PACIO Functional Status)Each functional status observation in the collection.
... derivedFrom SΣ0..*Reference(QuestionnaireResponse)Should point back to the QuestionnaireResponse that this resource is derived from.
... component Σ0..*BackboneElementCurrently not used in FunctionalStatusCollection.
.... id 0..1stringUnique id for inter-element referencing
.... extension 0..*ExtensionAdditional content defined by implementations
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... code Σ1..1CodeableConceptType of component observation (code / type)
Binding: LOINCCodes (example): Codes identifying names of simple observations.

.... value[x] Σ0..1Actual component result
..... valueQuantityQuantity
..... valueCodeableConceptCodeableConcept
..... valueStringstring
..... valueBooleanboolean
..... valueIntegerinteger
..... valueRangeRange
..... valueRatioRatio
..... valueSampledDataSampledData
..... valueTimetime
..... valueDateTimedateTime
..... valuePeriodPeriod
.... dataAbsentReason I0..1CodeableConceptWhy the component result is missing
Binding: DataAbsentReason (extensible): Codes specifying why the result (Observation.value[x]) is missing.

.... interpretation 0..*CodeableConceptHigh, low, normal, etc.
Binding: ObservationInterpretationCodes (extensible): Codes identifying interpretations of observations.


.... referenceRange 0..*See referenceRange (Observation)Provides guide for interpretation of component result

doco Documentation for this format

 

Other representations of profile: CSV, Excel, Schematron

Terminology Bindings

PathConformanceValueSet
Observation.languagepreferredCommonLanguages
Max Binding: AllLanguages
Observation.statusrequiredObservationStatus
Observation.categorypreferredObservationCategoryCodes
Observation.category:functioningextensiblePACIOFunctioningCategoryVS
Observation.codeextensibleLOINCCodes
Observation.dataAbsentReasonextensibleDataAbsentReason
Observation.interpretationextensibleObservationInterpretationCodes
Observation.bodySiteexampleSNOMEDCTBodyStructures
Observation.methodexampleObservationMethods
Observation.referenceRange.typepreferredObservationReferenceRangeMeaningCodes
Observation.referenceRange.appliesToexampleObservationReferenceRangeAppliesToCodes
Observation.component.codeexampleLOINCCodes
Observation.component.dataAbsentReasonextensibleDataAbsentReason
Observation.component.interpretationextensibleObservationInterpretationCodes