PACIO Personal Functioning and Engagement Implementation Guide
3.0.0-ballot - STU 3 Ballot United States of America flag

PACIO Personal Functioning and Engagement Implementation Guide, published by HL7 International / Patient Care. This guide is not an authorized publication; it is the continuous build for version 3.0.0-ballot built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/fhir-pacio-pfe/ and changes regularly. See the Directory of published versions

Resource Profile: Personal Functioning and Engagement Collection

Official URL: http://hl7.org/fhir/us/pacio-pfe/StructureDefinition/pfe-collection Version: 3.0.0-ballot
Standards status: Trial-use Maturity Level: 3 Computable Name: PFECollection
Other Identifiers: OID:2.16.840.1.113883.4.642.40.67.42.4

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.

Example Usage Scenarios:

The following are example usage scenarios for this Profile:

  • Query for the documentation of a formal panel of assessment questions related to a patient's functioning and engagement.
  • Record or update observations related to collections of assessment questions for a Patient.

Mandatory and Must Support Data Elements

The following data elements must always be present or must be supported if the data is present in the sending system (Must Support definition). They are presented below with a simple human-readable explanation. Profile specific guidance and examples are provided as well. The Formal Profile Definition below provides the formal summary, definitions, and terminology requirements.

Each Personal Functioning and Engagement Collection must have:

  1. a status
  2. a category code of "survey" and "functioning"
  3. a code representing the specific panel
  4. a patient
  5. the point in time or period when the observation was made
  6. who made the observation

Each Personal Functioning and Engagement Collection must support:

  1. the location the observation was made
  2. any devices the patient used
  3. an additional category value or values specifying the specific health or health-related domain that this observation is related to**
  4. related questionnaire responses that this observation is made from
  5. references to nested collections*

* ** see guidance below

Profile specific implementation guidance:

  • * These collection observations represent structured instruments and panels with multiple questions. The hasMember element SHALL be used to point to child Observation instances that contain the specific questions and answers, represented by Single Observations or nested panels represented by this profile.§CONF-2 The Observation.value and Observation.component elements SHALL be empty.§CONF-3
  • ** When a health or health-related domain is specified as an additional category value, Observation.code SHOULD be drawn from the corresponding domain-based value set as discussed below and on the domains page.§CONF-4

***Panel codes are not in scope for inclusion within domain-based value sets within STU1 of the PFE IG while the PACIO community determines how best to apply domains to panels that may have specific observations from multiple domains as descendents. In the meantime, the recommendation is not to include domain categories within Collection observation instances.

Usages:

You can also check for usages in the FHIR IG Statistics

Formal Views of Profile Content

Description Differentials, Snapshots, and other representations.

NameFlagsCard.TypeDescription & Constraints    Filter: doco
Observation C 0..* USCoreSimpleObservationProfile(9.0.0) assessment observation
Constraints: obs-6, obs-7
Observation.implicitRules This element is a modifier element. This element is included in summaries. 0..1 uri A set of rules under which this content was created
Observation.Slices for extension 0..* Extension Extension
Slice: Unordered, Open by value:url
Observation.Slices for extension.extension:event-location This element must be supported. 0..1 Reference(US Core Location Profile(9.0.0)) An extension to indicate where the observation event occurred.
URL: http://hl7.org/fhir/StructureDefinition/event-location profiled by http://hl7.org/fhir/us/pacio-pfe/StructureDefinition/event-location
Observation.Slices for extension.extension:device-use This element must be supported. 0..* Reference(Personal Functioning and Engagement Use of Device) An extension to indicate a record of assistive device usage by a patient during an assessment.
URL: http://hl7.org/fhir/us/pacio-pfe/StructureDefinition/device-patient-used
Observation.modifierExtension This element is a modifier element. 0..* Extension Extensions that cannot be ignored
Observation.status This element is a modifier element. This element must be supported. This element is included in summaries. 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: ObservationStatus (required): Codes providing the status of an observation.
Observation.Slices for category This element must be supported. 2..* CodeableConcept Classification of type of observation
Slice: Unordered, Open by value:$this
Binding: USCoreSimpleObservationCategory (9.0.0) (preferred): FHIR and US Core codes for high level observation categories.

Slicing Note: The rules on this element (including its children) apply to all the slices, but are not repeated in them
Observation.Slices for category.category:us-core This element must be supported. 1..2 CodeableConcept 𝗔𝗗𝗗𝗜𝗧𝗜𝗢𝗡𝗔𝗟 𝗨𝗦𝗖𝗗𝗜: US Core classification of type of observation
Binding: Personal Functioning and Engagement US Core Value Set (required)
Observation.Slices for category.category:survey This element must be supported. 1..1 CodeableConcept Classification of type of observation
Binding: ObservationCategoryCodes (preferred): Codes for high level observation categories.

Required Pattern:
{
  "coding" : [
    {
      "system" : "http://terminology.hl7.org/CodeSystem/observation-category",
      "code" : "survey"
    }
  ]
}
Observation.Slices for category.category:PFEDomain This element must be supported. 0..* CodeableConcept Classification of type of observation
Binding: Personal Functioning and Engagement Category Value Set (required)
Observation.code This element must be supported. This element is included in summaries. 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: LOINCCodes (preferred)
Observation.subject This element must be supported. This element is included in summaries. 1..1 Reference(US Core Patient Profile(9.0.0) This type must be supported. | Group | US Core Device Profile | US Core Location Profile(9.0.0)) Who and/or what the observation is about
Observation.effective[x] This element must be supported. This element is included in summaries. 1..1 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).
Observation.effective[x].effectiveDateTime dateTime This target must be supported.
Observation.effective[x].effectivePeriod Period
Observation.performer This element must be supported. This element is included in summaries. 1..* Reference(US Core Practitioner Profile(9.0.0) | US Core PractitionerRole Profile(9.0.0) | US Core Organization Profile(9.0.0)) 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.
Observation.method 0..1 CodeableConcept How it was done
Binding: SDOHCC ValueSet Observation Method (example)
Observation.hasMember This element must be supported. This element is included in summaries. 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.
Observation.derivedFrom This element must be supported. This element is included in summaries. 0..* Reference(US Core QuestionnaireResponse Profile(9.0.0) | US Core Simple Observation Profile(9.0.0)) Should point back to the QuestionnaireResponse that this resource is derived from.

doco Documentation for this format

Terminology Bindings

Path Status Usage ValueSet Version Source
Observation.status Base required ObservationStatus 📍4.0.1 FHIR Std.
Observation.category Base preferred US Core Simple Observation Category 📍9.0.0 US Core v9.0
Observation.category:us-core Base required Personal Functioning and Engagement US Core Value Set 📦3.0.0-ballot This IG
Observation.category:survey Base preferred Observation Category Codes 📍4.0.1 FHIR Std.
Observation.category:PFEDomain Base required Personal Functioning and Engagement Category Value Set 📦3.0.0-ballot This IG
Observation.code Base preferred LOINC Codes 📍4.0.1 FHIR Std.
Observation.method Base example SDOHCC ValueSet Observation Method 📦3.0.0 SDOH Clinical Care v3.0
Observation.component.​code Base example LOINC Codes 📍4.0.1 FHIR Std.

Constraints

Id Grade Path(s) Description Expression

This structure is derived from USCoreSimpleObservationProfile

NameFlagsCard.TypeDescription & Constraints    Filter: doco
Observation 0..* USCoreSimpleObservationProfile(9.0.0) assessment observation
Observation.Slices for extension 0..* Extension Extension
Slice: Unordered, Open by value:url
Observation.Slices for extension.extension:event-location This element must be supported. 0..1 Reference(US Core Location Profile(9.0.0)) An extension to indicate where the observation event occurred.
URL: http://hl7.org/fhir/StructureDefinition/event-location profiled by http://hl7.org/fhir/us/pacio-pfe/StructureDefinition/event-location
Observation.Slices for extension.extension:device-use This element must be supported. 0..* Reference(Personal Functioning and Engagement Use of Device) An extension to indicate a record of assistive device usage by a patient during an assessment.
URL: http://hl7.org/fhir/us/pacio-pfe/StructureDefinition/device-patient-used
Observation.status 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.
Observation.category 2..* CodeableConcept Classification of type of observation
Observation.Slices for category.category:us-core This element must be supported. 1..2 CodeableConcept 𝗔𝗗𝗗𝗜𝗧𝗜𝗢𝗡𝗔𝗟 𝗨𝗦𝗖𝗗𝗜: US Core classification of type of observation
Binding: Personal Functioning and Engagement US Core Value Set (required)
Observation.Slices for category.category:survey This element must be supported. 1..1 CodeableConcept Classification of type of observation
Required Pattern:
{
  "coding" : [
    {
      "system" : "http://terminology.hl7.org/CodeSystem/observation-category",
      "code" : "survey"
    }
  ]
}
Observation.Slices for category.category:PFEDomain This element must be supported. 0..* CodeableConcept Classification of type of observation
Binding: Personal Functioning and Engagement Category Value Set (required)
Observation.code 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.
Observation.effective[x] 1..1 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).
Observation.effective[x].effectiveDateTime dateTime
Observation.effective[x].effectivePeriod Period
Observation.performer 1..* Reference(US Core Practitioner Profile(9.0.0) | US Core PractitionerRole Profile(9.0.0) | US Core Organization Profile(9.0.0)) 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.
Observation.value[x] 0..0 Actual result
Observation.method 0..1 CodeableConcept How it was done
Binding: SDOHCC ValueSet Observation Method (example)
Observation.hasMember This element must be supported. 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.
Observation.derivedFrom This element must be supported. 0..* Reference(US Core QuestionnaireResponse Profile(9.0.0) | US Core Simple Observation Profile(9.0.0)) Should point back to the QuestionnaireResponse that this resource is derived from.
Observation.component 0..0 Component results

doco Documentation for this format

Terminology Bindings (Differential)

Path Status Usage ValueSet Version Source
Observation.category:us-core Base required Personal Functioning and Engagement US Core Value Set 📦3.0.0-ballot This IG
Observation.category:PFEDomain Base required Personal Functioning and Engagement Category Value Set 📦3.0.0-ballot This IG
Observation.method Base example SDOHCC ValueSet Observation Method 📦3.0.0 SDOH Clinical Care v3.0
NameFlagsCard.TypeDescription & Constraints    Filter: doco
Observation C 0..* USCoreSimpleObservationProfile(9.0.0) assessment observation
Constraints: obs-6, obs-7
Observation.id This element is included in summaries. 0..1 id Logical id of this artifact
Observation.meta This element is included in summaries. 0..1 Meta Metadata about the resource
Observation.implicitRules This element is a modifier element. This element is included in summaries. 0..1 uri A set of rules under which this content was created
Observation.language 0..1 code Language of the resource content
Binding: CommonLanguages (preferred): A human language.
Additional BindingsPurpose
AllLanguages Max Binding
Observation.text 0..1 Narrative Text summary of the resource, for human interpretation
This profile does not constrain the narrative in regard to content, language, or traceability to data elements
Observation.contained 0..* Resource Contained, inline Resources
Observation.Slices for extension 0..* Extension Extension
Slice: Unordered, Open by value:url
Observation.Slices for extension.extension:event-location This element must be supported. 0..1 Reference(US Core Location Profile(9.0.0)) An extension to indicate where the observation event occurred.
URL: http://hl7.org/fhir/StructureDefinition/event-location profiled by http://hl7.org/fhir/us/pacio-pfe/StructureDefinition/event-location
Observation.Slices for extension.extension:device-use This element must be supported. 0..* Reference(Personal Functioning and Engagement Use of Device) An extension to indicate a record of assistive device usage by a patient during an assessment.
URL: http://hl7.org/fhir/us/pacio-pfe/StructureDefinition/device-patient-used
Observation.modifierExtension This element is a modifier element. 0..* Extension Extensions that cannot be ignored
Observation.identifier This element is included in summaries. 0..* Identifier Business Identifier for observation
Observation.basedOn This element is included in summaries. 0..* Reference(CarePlan | DeviceRequest | ImmunizationRecommendation | MedicationRequest | NutritionOrder | ServiceRequest) Fulfills plan, proposal or order
Observation.partOf This element is included in summaries. 0..* Reference(MedicationAdministration | MedicationDispense | MedicationStatement | Procedure | Immunization | ImagingStudy) Part of referenced event
Observation.status This element is a modifier element. This element must be supported. This element is included in summaries. 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: ObservationStatus (required): Codes providing the status of an observation.
Observation.Slices for category This element must be supported. 2..* CodeableConcept Classification of type of observation
Slice: Unordered, Open by value:$this
Binding: USCoreSimpleObservationCategory (9.0.0) (preferred): FHIR and US Core codes for high level observation categories.

Slicing Note: The rules on this element (including its children) apply to all the slices, but are not repeated in them
Observation.Slices for category.category:us-core This element must be supported. 1..2 CodeableConcept 𝗔𝗗𝗗𝗜𝗧𝗜𝗢𝗡𝗔𝗟 𝗨𝗦𝗖𝗗𝗜: US Core classification of type of observation
Binding: Personal Functioning and Engagement US Core Value Set (required)
Observation.Slices for category.category:survey This element must be supported. 1..1 CodeableConcept Classification of type of observation
Binding: ObservationCategoryCodes (preferred): Codes for high level observation categories.

Required Pattern:
{
  "coding" : [
    {
      "system" : "http://terminology.hl7.org/CodeSystem/observation-category",
      "code" : "survey"
    }
  ]
}
Observation.Slices for category.category:PFEDomain This element must be supported. 0..* CodeableConcept Classification of type of observation
Binding: Personal Functioning and Engagement Category Value Set (required)
Observation.code This element must be supported. This element is included in summaries. 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: LOINCCodes (preferred)
Observation.subject This element must be supported. This element is included in summaries. 1..1 Reference(US Core Patient Profile(9.0.0) This type must be supported. | Group | US Core Device Profile | US Core Location Profile(9.0.0)) Who and/or what the observation is about
Observation.focus This element is included in summaries. 0..* Reference(Resource) What the observation is about, when it is not about the subject of record
Observation.encounter This element is included in summaries. 0..1 Reference(Encounter) Healthcare event during which this observation is made
Observation.effective[x] This element must be supported. This element is included in summaries. 1..1 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).
Observation.effective[x].effectiveDateTime dateTime This target must be supported.
Observation.effective[x].effectivePeriod Period
Observation.issued This element is included in summaries. 0..1 instant Date/Time this version was made available
Observation.performer This element must be supported. This element is included in summaries. 1..* Reference(US Core Practitioner Profile(9.0.0) | US Core PractitionerRole Profile(9.0.0) | US Core Organization Profile(9.0.0)) 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.
Observation.dataAbsentReason C 0..1 CodeableConcept Why the result is missing
Binding: DataAbsentReason (extensible): Codes specifying why the result (Observation.value[x]) is missing.
Observation.interpretation 0..* CodeableConcept High, low, normal, etc.
Binding: ObservationInterpretationCodes (extensible): Codes identifying interpretations of observations.
Observation.note 0..* Annotation Comments about the observation
Observation.bodySite 0..1 CodeableConcept Observed body part
Binding: SNOMEDCTBodyStructures (example): Codes describing anatomical locations. May include laterality.
Observation.method 0..1 CodeableConcept How it was done
Binding: SDOHCC ValueSet Observation Method (example)
Observation.specimen 0..1 Reference(Specimen) Specimen used for this observation
Observation.device 0..1 Reference(Device | DeviceMetric) (Measurement) Device
Observation.referenceRange C 0..* BackboneElement Provides guide for interpretation
Constraints: obs-3
Observation.referenceRange.id 0..1 string Unique id for inter-element referencing
Observation.referenceRange.extension 0..* Extension Additional content defined by implementations
Observation.referenceRange.modifierExtension This element is a modifier element. This element is included in summaries. 0..* Extension Extensions that cannot be ignored even if unrecognized
Observation.referenceRange.low C 0..1 SimpleQuantity(4.0.1) Low Range, if relevant
Constraints: sqty-1
Observation.referenceRange.high C 0..1 SimpleQuantity(4.0.1) High Range, if relevant
Constraints: sqty-1
Observation.referenceRange.type 0..1 CodeableConcept Reference range qualifier
Binding: ObservationReferenceRangeMeaningCodes (preferred): Code for the meaning of a reference range.
Observation.referenceRange.appliesTo 0..* CodeableConcept Reference range population
Binding: ObservationReferenceRangeAppliesToCodes (example): Codes identifying the population the reference range applies to.
Observation.referenceRange.age 0..1 Range Applicable age range, if relevant
Observation.referenceRange.text 0..1 string Text based reference range in an observation
Observation.hasMember This element must be supported. This element is included in summaries. 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.
Observation.derivedFrom This element must be supported. This element is included in summaries. 0..* Reference(US Core QuestionnaireResponse Profile(9.0.0) | US Core Simple Observation Profile(9.0.0)) Should point back to the QuestionnaireResponse that this resource is derived from.

doco Documentation for this format

Terminology Bindings

Path Status Usage ValueSet Version Source
Observation.language Base preferred Common Languages 📍4.0.1 FHIR Std.
Observation.status Base required ObservationStatus 📍4.0.1 FHIR Std.
Observation.category Base preferred US Core Simple Observation Category 📍9.0.0 US Core v9.0
Observation.category:us-core Base required Personal Functioning and Engagement US Core Value Set 📦3.0.0-ballot This IG
Observation.category:survey Base preferred Observation Category Codes 📍4.0.1 FHIR Std.
Observation.category:PFEDomain Base required Personal Functioning and Engagement Category Value Set 📦3.0.0-ballot This IG
Observation.code Base preferred LOINC Codes 📍4.0.1 FHIR Std.
Observation.dataAbsentReason Base extensible DataAbsentReason 📍4.0.1 FHIR Std.
Observation.interpretation Base extensible Observation Interpretation Codes 📍4.0.1 FHIR Std.
Observation.bodySite Base example SNOMED CT Body Structures 📍4.0.1 FHIR Std.
Observation.method Base example SDOHCC ValueSet Observation Method 📦3.0.0 SDOH Clinical Care v3.0
Observation.referenceRange.​type Base preferred Observation Reference Range Meaning Codes 📍4.0.1 FHIR Std.
Observation.referenceRange.​appliesTo Base example Observation Reference Range Applies To Codes 📍4.0.1 FHIR Std.
Observation.component.​code Base example LOINC Codes 📍4.0.1 FHIR Std.
Observation.component.​dataAbsentReason Base extensible DataAbsentReason 📍4.0.1 FHIR Std.
Observation.component.​interpretation Base extensible Observation Interpretation Codes 📍4.0.1 FHIR Std.

Constraints

Id Grade Path(s) Description Expression

Key Elements View

NameFlagsCard.TypeDescription & Constraints    Filter: doco
Observation C 0..* USCoreSimpleObservationProfile(9.0.0) assessment observation
Constraints: obs-6, obs-7
Observation.implicitRules This element is a modifier element. This element is included in summaries. 0..1 uri A set of rules under which this content was created
Observation.Slices for extension 0..* Extension Extension
Slice: Unordered, Open by value:url
Observation.Slices for extension.extension:event-location This element must be supported. 0..1 Reference(US Core Location Profile(9.0.0)) An extension to indicate where the observation event occurred.
URL: http://hl7.org/fhir/StructureDefinition/event-location profiled by http://hl7.org/fhir/us/pacio-pfe/StructureDefinition/event-location
Observation.Slices for extension.extension:device-use This element must be supported. 0..* Reference(Personal Functioning and Engagement Use of Device) An extension to indicate a record of assistive device usage by a patient during an assessment.
URL: http://hl7.org/fhir/us/pacio-pfe/StructureDefinition/device-patient-used
Observation.modifierExtension This element is a modifier element. 0..* Extension Extensions that cannot be ignored
Observation.status This element is a modifier element. This element must be supported. This element is included in summaries. 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: ObservationStatus (required): Codes providing the status of an observation.
Observation.Slices for category This element must be supported. 2..* CodeableConcept Classification of type of observation
Slice: Unordered, Open by value:$this
Binding: USCoreSimpleObservationCategory (9.0.0) (preferred): FHIR and US Core codes for high level observation categories.

Slicing Note: The rules on this element (including its children) apply to all the slices, but are not repeated in them
Observation.Slices for category.category:us-core This element must be supported. 1..2 CodeableConcept 𝗔𝗗𝗗𝗜𝗧𝗜𝗢𝗡𝗔𝗟 𝗨𝗦𝗖𝗗𝗜: US Core classification of type of observation
Binding: Personal Functioning and Engagement US Core Value Set (required)
Observation.Slices for category.category:survey This element must be supported. 1..1 CodeableConcept Classification of type of observation
Binding: ObservationCategoryCodes (preferred): Codes for high level observation categories.

Required Pattern:
{
  "coding" : [
    {
      "system" : "http://terminology.hl7.org/CodeSystem/observation-category",
      "code" : "survey"
    }
  ]
}
Observation.Slices for category.category:PFEDomain This element must be supported. 0..* CodeableConcept Classification of type of observation
Binding: Personal Functioning and Engagement Category Value Set (required)
Observation.code This element must be supported. This element is included in summaries. 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: LOINCCodes (preferred)
Observation.subject This element must be supported. This element is included in summaries. 1..1 Reference(US Core Patient Profile(9.0.0) This type must be supported. | Group | US Core Device Profile | US Core Location Profile(9.0.0)) Who and/or what the observation is about
Observation.effective[x] This element must be supported. This element is included in summaries. 1..1 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).
Observation.effective[x].effectiveDateTime dateTime This target must be supported.
Observation.effective[x].effectivePeriod Period
Observation.performer This element must be supported. This element is included in summaries. 1..* Reference(US Core Practitioner Profile(9.0.0) | US Core PractitionerRole Profile(9.0.0) | US Core Organization Profile(9.0.0)) 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.
Observation.method 0..1 CodeableConcept How it was done
Binding: SDOHCC ValueSet Observation Method (example)
Observation.hasMember This element must be supported. This element is included in summaries. 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.
Observation.derivedFrom This element must be supported. This element is included in summaries. 0..* Reference(US Core QuestionnaireResponse Profile(9.0.0) | US Core Simple Observation Profile(9.0.0)) Should point back to the QuestionnaireResponse that this resource is derived from.

doco Documentation for this format

Terminology Bindings

Path Status Usage ValueSet Version Source
Observation.status Base required ObservationStatus 📍4.0.1 FHIR Std.
Observation.category Base preferred US Core Simple Observation Category 📍9.0.0 US Core v9.0
Observation.category:us-core Base required Personal Functioning and Engagement US Core Value Set 📦3.0.0-ballot This IG
Observation.category:survey Base preferred Observation Category Codes 📍4.0.1 FHIR Std.
Observation.category:PFEDomain Base required Personal Functioning and Engagement Category Value Set 📦3.0.0-ballot This IG
Observation.code Base preferred LOINC Codes 📍4.0.1 FHIR Std.
Observation.method Base example SDOHCC ValueSet Observation Method 📦3.0.0 SDOH Clinical Care v3.0
Observation.component.​code Base example LOINC Codes 📍4.0.1 FHIR Std.

Constraints

Id Grade Path(s) Description Expression

Differential View

This structure is derived from USCoreSimpleObservationProfile

NameFlagsCard.TypeDescription & Constraints    Filter: doco
Observation 0..* USCoreSimpleObservationProfile(9.0.0) assessment observation
Observation.Slices for extension 0..* Extension Extension
Slice: Unordered, Open by value:url
Observation.Slices for extension.extension:event-location This element must be supported. 0..1 Reference(US Core Location Profile(9.0.0)) An extension to indicate where the observation event occurred.
URL: http://hl7.org/fhir/StructureDefinition/event-location profiled by http://hl7.org/fhir/us/pacio-pfe/StructureDefinition/event-location
Observation.Slices for extension.extension:device-use This element must be supported. 0..* Reference(Personal Functioning and Engagement Use of Device) An extension to indicate a record of assistive device usage by a patient during an assessment.
URL: http://hl7.org/fhir/us/pacio-pfe/StructureDefinition/device-patient-used
Observation.status 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.
Observation.category 2..* CodeableConcept Classification of type of observation
Observation.Slices for category Content/Rules for all slices
Observation.Slices for category.category:us-core This element must be supported. 1..2 CodeableConcept 𝗔𝗗𝗗𝗜𝗧𝗜𝗢𝗡𝗔𝗟 𝗨𝗦𝗖𝗗𝗜: US Core classification of type of observation
Binding: Personal Functioning and Engagement US Core Value Set (required)
Observation.Slices for category.category:survey This element must be supported. 1..1 CodeableConcept Classification of type of observation
Required Pattern:
{
  "coding" : [
    {
      "system" : "http://terminology.hl7.org/CodeSystem/observation-category",
      "code" : "survey"
    }
  ]
}
Observation.Slices for category.category:PFEDomain This element must be supported. 0..* CodeableConcept Classification of type of observation
Binding: Personal Functioning and Engagement Category Value Set (required)
Observation.code 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.
Observation.effective[x] 1..1 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).
Observation.effective[x].effectiveDateTime dateTime
Observation.effective[x].effectivePeriod Period
Observation.performer 1..* Reference(US Core Practitioner Profile(9.0.0) | US Core PractitionerRole Profile(9.0.0) | US Core Organization Profile(9.0.0)) 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.
Observation.value[x] 0..0 Actual result
Observation.method 0..1 CodeableConcept How it was done
Binding: SDOHCC ValueSet Observation Method (example)
Observation.hasMember This element must be supported. 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.
Observation.derivedFrom This element must be supported. 0..* Reference(US Core QuestionnaireResponse Profile(9.0.0) | US Core Simple Observation Profile(9.0.0)) Should point back to the QuestionnaireResponse that this resource is derived from.
Observation.component 0..0 Component results

doco Documentation for this format

Terminology Bindings (Differential)

Path Status Usage ValueSet Version Source
Observation.category:us-core Base required Personal Functioning and Engagement US Core Value Set 📦3.0.0-ballot This IG
Observation.category:PFEDomain Base required Personal Functioning and Engagement Category Value Set 📦3.0.0-ballot This IG
Observation.method Base example SDOHCC ValueSet Observation Method 📦3.0.0 SDOH Clinical Care v3.0

Snapshot ViewView

NameFlagsCard.TypeDescription & Constraints    Filter: doco
Observation C 0..* USCoreSimpleObservationProfile(9.0.0) assessment observation
Constraints: obs-6, obs-7
Observation.id This element is included in summaries. 0..1 id Logical id of this artifact
Observation.meta This element is included in summaries. 0..1 Meta Metadata about the resource
Observation.implicitRules This element is a modifier element. This element is included in summaries. 0..1 uri A set of rules under which this content was created
Observation.language 0..1 code Language of the resource content
Binding: CommonLanguages (preferred): A human language.
Additional BindingsPurpose
AllLanguages Max Binding
Observation.text 0..1 Narrative Text summary of the resource, for human interpretation
This profile does not constrain the narrative in regard to content, language, or traceability to data elements
Observation.contained 0..* Resource Contained, inline Resources
Observation.Slices for extension 0..* Extension Extension
Slice: Unordered, Open by value:url
Observation.Slices for extension.extension:event-location This element must be supported. 0..1 Reference(US Core Location Profile(9.0.0)) An extension to indicate where the observation event occurred.
URL: http://hl7.org/fhir/StructureDefinition/event-location profiled by http://hl7.org/fhir/us/pacio-pfe/StructureDefinition/event-location
Observation.Slices for extension.extension:device-use This element must be supported. 0..* Reference(Personal Functioning and Engagement Use of Device) An extension to indicate a record of assistive device usage by a patient during an assessment.
URL: http://hl7.org/fhir/us/pacio-pfe/StructureDefinition/device-patient-used
Observation.modifierExtension This element is a modifier element. 0..* Extension Extensions that cannot be ignored
Observation.identifier This element is included in summaries. 0..* Identifier Business Identifier for observation
Observation.basedOn This element is included in summaries. 0..* Reference(CarePlan | DeviceRequest | ImmunizationRecommendation | MedicationRequest | NutritionOrder | ServiceRequest) Fulfills plan, proposal or order
Observation.partOf This element is included in summaries. 0..* Reference(MedicationAdministration | MedicationDispense | MedicationStatement | Procedure | Immunization | ImagingStudy) Part of referenced event
Observation.status This element is a modifier element. This element must be supported. This element is included in summaries. 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: ObservationStatus (required): Codes providing the status of an observation.
Observation.Slices for category This element must be supported. 2..* CodeableConcept Classification of type of observation
Slice: Unordered, Open by value:$this
Binding: USCoreSimpleObservationCategory (9.0.0) (preferred): FHIR and US Core codes for high level observation categories.

Slicing Note: The rules on this element (including its children) apply to all the slices, but are not repeated in them
Observation.Slices for category.category:us-core This element must be supported. 1..2 CodeableConcept 𝗔𝗗𝗗𝗜𝗧𝗜𝗢𝗡𝗔𝗟 𝗨𝗦𝗖𝗗𝗜: US Core classification of type of observation
Binding: Personal Functioning and Engagement US Core Value Set (required)
Observation.Slices for category.category:survey This element must be supported. 1..1 CodeableConcept Classification of type of observation
Binding: ObservationCategoryCodes (preferred): Codes for high level observation categories.

Required Pattern:
{
  "coding" : [
    {
      "system" : "http://terminology.hl7.org/CodeSystem/observation-category",
      "code" : "survey"
    }
  ]
}
Observation.Slices for category.category:PFEDomain This element must be supported. 0..* CodeableConcept Classification of type of observation
Binding: Personal Functioning and Engagement Category Value Set (required)
Observation.code This element must be supported. This element is included in summaries. 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: LOINCCodes (preferred)
Observation.subject This element must be supported. This element is included in summaries. 1..1 Reference(US Core Patient Profile(9.0.0) This type must be supported. | Group | US Core Device Profile | US Core Location Profile(9.0.0)) Who and/or what the observation is about
Observation.focus This element is included in summaries. 0..* Reference(Resource) What the observation is about, when it is not about the subject of record
Observation.encounter This element is included in summaries. 0..1 Reference(Encounter) Healthcare event during which this observation is made
Observation.effective[x] This element must be supported. This element is included in summaries. 1..1 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).
Observation.effective[x].effectiveDateTime dateTime This target must be supported.
Observation.effective[x].effectivePeriod Period
Observation.issued This element is included in summaries. 0..1 instant Date/Time this version was made available
Observation.performer This element must be supported. This element is included in summaries. 1..* Reference(US Core Practitioner Profile(9.0.0) | US Core PractitionerRole Profile(9.0.0) | US Core Organization Profile(9.0.0)) 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.
Observation.dataAbsentReason C 0..1 CodeableConcept Why the result is missing
Binding: DataAbsentReason (extensible): Codes specifying why the result (Observation.value[x]) is missing.
Observation.interpretation 0..* CodeableConcept High, low, normal, etc.
Binding: ObservationInterpretationCodes (extensible): Codes identifying interpretations of observations.
Observation.note 0..* Annotation Comments about the observation
Observation.bodySite 0..1 CodeableConcept Observed body part
Binding: SNOMEDCTBodyStructures (example): Codes describing anatomical locations. May include laterality.
Observation.method 0..1 CodeableConcept How it was done
Binding: SDOHCC ValueSet Observation Method (example)
Observation.specimen 0..1 Reference(Specimen) Specimen used for this observation
Observation.device 0..1 Reference(Device | DeviceMetric) (Measurement) Device
Observation.referenceRange C 0..* BackboneElement Provides guide for interpretation
Constraints: obs-3
Observation.referenceRange.id 0..1 string Unique id for inter-element referencing
Observation.referenceRange.extension 0..* Extension Additional content defined by implementations
Observation.referenceRange.modifierExtension This element is a modifier element. This element is included in summaries. 0..* Extension Extensions that cannot be ignored even if unrecognized
Observation.referenceRange.low C 0..1 SimpleQuantity(4.0.1) Low Range, if relevant
Constraints: sqty-1
Observation.referenceRange.high C 0..1 SimpleQuantity(4.0.1) High Range, if relevant
Constraints: sqty-1
Observation.referenceRange.type 0..1 CodeableConcept Reference range qualifier
Binding: ObservationReferenceRangeMeaningCodes (preferred): Code for the meaning of a reference range.
Observation.referenceRange.appliesTo 0..* CodeableConcept Reference range population
Binding: ObservationReferenceRangeAppliesToCodes (example): Codes identifying the population the reference range applies to.
Observation.referenceRange.age 0..1 Range Applicable age range, if relevant
Observation.referenceRange.text 0..1 string Text based reference range in an observation
Observation.hasMember This element must be supported. This element is included in summaries. 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.
Observation.derivedFrom This element must be supported. This element is included in summaries. 0..* Reference(US Core QuestionnaireResponse Profile(9.0.0) | US Core Simple Observation Profile(9.0.0)) Should point back to the QuestionnaireResponse that this resource is derived from.

doco Documentation for this format

Terminology Bindings

Path Status Usage ValueSet Version Source
Observation.language Base preferred Common Languages 📍4.0.1 FHIR Std.
Observation.status Base required ObservationStatus 📍4.0.1 FHIR Std.
Observation.category Base preferred US Core Simple Observation Category 📍9.0.0 US Core v9.0
Observation.category:us-core Base required Personal Functioning and Engagement US Core Value Set 📦3.0.0-ballot This IG
Observation.category:survey Base preferred Observation Category Codes 📍4.0.1 FHIR Std.
Observation.category:PFEDomain Base required Personal Functioning and Engagement Category Value Set 📦3.0.0-ballot This IG
Observation.code Base preferred LOINC Codes 📍4.0.1 FHIR Std.
Observation.dataAbsentReason Base extensible DataAbsentReason 📍4.0.1 FHIR Std.
Observation.interpretation Base extensible Observation Interpretation Codes 📍4.0.1 FHIR Std.
Observation.bodySite Base example SNOMED CT Body Structures 📍4.0.1 FHIR Std.
Observation.method Base example SDOHCC ValueSet Observation Method 📦3.0.0 SDOH Clinical Care v3.0
Observation.referenceRange.​type Base preferred Observation Reference Range Meaning Codes 📍4.0.1 FHIR Std.
Observation.referenceRange.​appliesTo Base example Observation Reference Range Applies To Codes 📍4.0.1 FHIR Std.
Observation.component.​code Base example LOINC Codes 📍4.0.1 FHIR Std.
Observation.component.​dataAbsentReason Base extensible DataAbsentReason 📍4.0.1 FHIR Std.
Observation.component.​interpretation Base extensible Observation Interpretation Codes 📍4.0.1 FHIR Std.

Constraints

Id Grade Path(s) Description Expression

 

Other representations of profile: CSV, Excel, Schematron

Notes:

The syntax used to describe the interactions below is described here.

Mandatory Search Parameters:

The mandatory search parameter combinations are defined below:

  1. SHALL support searching using the combination of the patient and category search parameters:§CONF-5

    GET [base]/Observation?patient={Type/}[id]&category={system|}[code]

    Example:

    1. GET [base]/Observation?patient=1134281&category=http://terminology.hl7.org/CodeSystem/observation-category|survey
    2. GET [base]/Observation?patient=1134281&category=http://hl7.org/fhir/sid/icf|mental_functions

    Implementation Notes: Fetches a bundle of all Observation resources for the specified patient and a category code = survey or mental_functions respectively (how to search by reference and how to search by token)

  2. SHALL support searching using the combination of the patient and code search parameters:§CONF-6
    • including optional support for OR search on code (e.g.code={system|}[code],{system|}[code],...)

    GET [base]/Observation?patient={Type/}[id]&code={system|}[code]{,{system|}[code],...}

    Example:

    1. GET [base]/Observation?patient=1134281&code=http://loinc.org|72133-2
    2. GET [base]/Observation?patient=1134281&code=http://loinc.org|72133-2,http://loinc.org|72107-6,http://loinc.org|54635-8

    Implementation Notes: Fetches a bundle of all Observation resources for the specified patient and observation code(s). SHOULD support search by multiple report codes.§CONF-7 The Observation code parameter searches `Observation.code only. (how to search by reference and how to search by token)

  3. SHALL support searching using the combination of the patient and category and date search parameters:§CONF-8
    • including support for these date comparators: gt,lt,ge,le
    • including optional support for AND search on date (e.g.date=[date]&date=[date]]&...)

    GET [base]/Observation?patient={Type/}[id]&category={system|}[code]&date={gt|lt|ge|le}[date]{&date={gt|lt|ge|le}[date]&...}

    Example:

    1. GET [base]Observation?patient=555580&category=http://terminology.hl7.org/CodeSystem/observation-category|survey&date=ge2018-03-14T00:00:00Z
    2. GET [base]Observation?patient=555580&category=http://hl7.org/fhir/sid/icf|mental_functions&date=ge2018-03-14T00:00:00Z

    Implementation Notes: Fetches a bundle of all Observation resources for the specified patient and date and a category code = survey or mental_functions respectively (how to search by reference and how to search by token and how to search by date)

Optional Search Parameters:

The optional search parameter combinations are defined below:

  1. SHOULD support searching using the combination of the patient and category and status search parameters:§CONF-9
    • including support for OR search on status (e.g.status={system|}[code],{system|}[code],...)

    GET [base]/Observation?patient={Type/}[id]&category={system|}[code]&status={system|}[code]{,{system|}[code],...}

    Example:

    1. GET [base]/Observation?patient=1134281&category=http://terminology.hl7.org/CodeSystem/observation-category|survey&status=final
    2. GET [base]/Observation?patient=1134281&category=http://hl7.org/fhir/sid/icf|mental_functions&status=final

    Implementation Notes: Fetches a bundle of all Observation resources for the specified patient and category = survey or mental_functions respectively and status final (how to search by reference and how to search by token)

  2. SHOULD support searching using the combination of the patient and code and date search parameters:§CONF-10
    • including optional support for OR search on code (e.g.code={system|}[code],{system|}[code],...)
    • including support for these date comparators: gt,lt,ge,le
    • including optional support for AND search on date (e.g.date=[date]&date=[date]]&...)

    GET [base]/Observation?patient={Type/}[id]&code={system|}[code]{,{system|}[code],...}&date={gt|lt|ge|le}[date]{&date={gt|lt|ge|le}[date]&...}

    Example:

    1. GET [base]Observation?patient=555580&code=http://loinc.org|72133-2&date=ge2019-01-01T00:00:00Z

    Implementation Notes: Fetches a bundle of all Observation resources for the specified patient and date and report code(s). SHOULD support search by multiple report codes.§CONF-11 (how to search by reference and how to search by token and how to search by date)