This page is part of the PACIO Functional Status Implementation Guide (v1.0.0: STU 1) based on FHIR R4. This is the current published version in its permanent home (it will always be available at this URL). For a full list of available versions, see the Directory of published versions
Contents:
This page provides a list of the FHIR artifacts defined as part of this implementation guide.
The following artifacts define the specific capabilities that different types of systems are expected to have in order to comply with this implementation guide. Systems conforming to this implementation guide are expected to declare conformance to one or more of the following capability statements.
PACIO Functional Status Capability Statement |
This Capability Statement defines the expected capabilities of a PACIO Functional Status FHIR server conforming to the PACIO functional Status Implementation Guide. |
These define constraints on FHIR resources for systems conforming to this implementation guide
PACIO Functional Status |
An exchange of functional status observation for a patient. This profile is used for exchanging a single observation data generally included in a set of observation data collected through the use of a structured resource (e.g. assessment tool, instrument, or screen). |
PACIO Functional Status Collection |
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). |
PACIO Narrative History of Functional Status |
An exchange of summary observation regarding the most recent prior level of function immediately preceding the current admission, illness, or exacerbation for a patient. The use of this profile is encouraged in the absence of formal prior level of function assessments. For formal assessments conducted with for example, an assessment instrument, use the Functional Status Collection and Functional Status profiles to capture assessment data. |
Use of Device |
A record of an assistive device–e.g. walker or wheelchair, being used by a patient during a functional status assessment. This profile based on the DeviceUseStatement resource provides a way to include information about device usage during an assessment. |
These define constraints on FHIR data types for systems conforming to this implementation guide
AssistanceRequired |
Associated with the Narrative History of Functional Status profile to provide a high-level indication of assistance required for the person’s baseline ability (physical function immediately preceding the current admission, illness, or exacerbation for a patient) to perform everyday activities. The CMS Assessment answer list LL4309-2 provides possible values for this extension. |
DevicePatientUsed |
Associated with the Funcational Status Collection profile to point to a record indicating what healthcare-related assistive device was used by a patient during a functional status assessment. This extension leverages the DeviceUseStatement resource instead of Device resource so as to indicate appropriately a record of assistive device usage by a patient. |
ObservationEventLocation |
This extension is used to indicate the principal physical location where an observation event occurred. |
These define sets of codes used by systems conforming to this implementation guide
PACIO Functioning Category Value Set |
Codes for the classification of patient observation. This is an extension of the ObservationCategoryCodes value set |
These define new code systems used by systems conforming to this implementation guide
PACIO Functioning Category Code System |
Defining a specific code for the classification of patient observation regarding individual’s functioning. |
These are example instances that show what data produced and consumed by systems conforming with this implementation guide might look like