This page is part of the PACIO Personal Functioning and Engagement Implementation Guide (v1.0.0: STU 1) based on FHIR (HL7® FHIR® Standard) R4. This is the current published version. For a full list of available versions, see the Directory of published versions
Home
Official URL: http://hl7.org/fhir/us/pacio-pfe/ImplementationGuide/hl7.fhir.us.pacio-pfe
The Personal Functioning and Engagement (PFE) HL7® FHIR® Implementation Guide (IG) supports the exchange of information related to a person’s ability to participate in activities and interact with their community and the environment around them. The three words in the title frame aspects of the intended scope for this IG:
Personal: in-scope data relates to the functioning of an individual person, as opposed to a group, system, or organization.
Functioning: in-scope data relates to what the person can do, the help they need, and the effects of contributing factors, including physiological, environmental, and personal conditions. The International Classification of Functioning, Disability, and Health (ICF), published by the World Health Organization (WHO), defines the term, “functioning,” as an umbrella term for body functions, activities, and participation.
Engagement: by promoting the exchange of in-scope data, this IG aspires to help individuals be active participants in their life, as opposed to passive observers.
Background
After a patient receives care in an acute hospital setting, they may move into post-acute care (PAC) settings like long-term care facilities (e.g., skilled nursing or assisted living facilitates) before going back into their homes and communities where they will manage their health themselves and with support from others (e.g., family, home health aides, community organizations that support basic needs). In these settings, the focus of their healthcare providers and caregivers is to: (1) deliver therapies and treatments; and (2) identify supports that will help the patient successfully engage in daily life at home and in the community.
While a patient is in long-term care, healthcare providers from many disciplines - including physicians, nurses, physical therapists, occupational therapists, speech and language pathologists, and social workers - use formal and informal assessments and observations to answer questions that can help them prepare a person to return home, such as:
What activities of daily living (ADLs), like bathing or dressing, does the patient have trouble engaging in?
What treatments and therapies would help the person improve their ability to engage in ADLs?
What supports will a person need to engage in ADLs, both now at the long-term care facility, and in the future when they have returned home?
What professional or community-based services will they need?
Are changes to their home or living situation necessary?
Do they need assistive devices?
Healthcare providers record assessments and observations in an electronic health record, which their colleagues and their organization can use for tracking improvement, care planning, and reimbursement purposes. Access to this information is critical for other healthcare providers and organizations across the full spectrum of the person’s care, including acute care, primary care, and home- and community-based services, to support care coordination across settings.
Unfortunately, healthcare providers across the spectrum of care, including at long-term care facilities and down-stream settings such as home- and community-based services, often face challenges sharing important assessment and observation data with and obtaining it from other healthcare providers involved in the person’s care. Forty-five percent of Medicare beneficiaries require post-acute care services after hospitalization (RTI International analysis of 2014 Medicare claims under contract with the Assistant Secretary for Planning and Evaluation, August 2018 (aea0315)), but a 2020 study that assessed continuity between hospitals and skilled nursing facilities (SNF) found that SNFs received complete mental status information at transition of care only 6% of the time. JAMA Network Open. 2021;4(1):e2033980. doi: 10.1001/jamanetworkopen.2020.33980. This failure to exchange accurate, timely data often leads to inefficient workflows, duplicative data entry, and increased risk of harm attributable to missing or inaccurate information.
The purpose of this IG is to offer a framework that providers and organizations across the spectrum of care can use to exchange observational assessment information. By using this framework to put accessible, usable, and timely data into the hands of providers, patients, and their caregivers, organizations can foster appropriate care for the whole person, promoting their ability to actively engage in daily life at home and in the community and supporting the person in achieving their optimal quality of life. This IG facilitates efforts to build more interoperable health IT systems that support data sharing, first outlined in the landmark Institute of Medicine Report To Err is Human: Building a Safer Health System, and is congruent with current federal efforts (e.g., The Centers for Medicare and Medicaid Services Promoting Interoperability Programs).
Why PACIO
The PACIO Project is a collaborative effort to advance interoperable health data exchange between PAC and other providers, patients, their caregivers, and key stakeholders across healthcare and to promote health data exchange in collaboration with policy makers, standards organizations, and industry through a consensus-based approach.
The primary goal of the PACIO Project is to establish the technical foundation for data exchange within PAC and partner organizations across the spectrum of care. It seeks to do so by creating a framework for and community through the development of Fast Healthcare Interoperability Resource (FHIR®) technical implementation guides (IGs) and reference implementations that will facilitate health data exchange through standards-based use case-driven application programming interfaces (APIs).
Information covered in this IG is relevant to providers across the full spectrum of patient care, including acute, sub-acute, long-term post-acute care (LTPAC), community based organizations, and private practice practitioners. The PACIO community brings together healthcare providers with a deep understanding of patient functioning that makes them uniquely suited to author this IG. This understanding comes out of providers’:
goal of helping individuals in these settings return to living in their homes and communities, and
knowledge of the activities that individuals need to perform and how to help them regain the ability to perform these activities by leveraging the necessary treatments and supports.
Domains
The scope of this IG is intentionally broad. It provides a framework within which to represent observations across many aspects of an individual’s functioning and engagement with their environment and the world. To further support the interoperability of systems based on this guide, the IG defines the domains tied to value sets that enumerate terminology codes for related observations. These domains are drawn from the World Health Organization’s (WHO) International Classification of Functioning, Disability and Health (commonly known as ICF). ICF was chosen as the source of domains because it takes a holistic view of a person through an interdisciplinary therapy lens, considers how best to support the person’s return to the community, and has been integrated into some EHRs. Examples of ICF categories the IG uses as domains include but are not limited to:
Mental functions, captured as a part of evaluating an individual’s cognitive status,
Mobility and Self-care, captured as a part of evaluating an individual’s functional status, and
More information on the domains currently defined in this IG, how codes are assigned to the domain-based value sets, and examples drawn from post-acute care assessments required by the IMPACT Act can be found on the Domain Support page. More information on all of the categories that ICF defines can be found in the ICF Browser.
IMPACT Act
One impetus for this IG is the amendment to the Social Security Act in 2014 to include the Improving Medicare Post-Acute Care Transformation (IMPACT) Act. The IMPACT Act requires the standardization and interoperability of patient assessments in specific categories for PAC settings, including long-term care hospitals (LTCHs), home health agencies (HHAs), SNFs, and inpatient rehabilitation facilities (IRFs). It focuses on the standardization of data elements in specified quality measure and patient assessment domains for cross-setting comparison and clinical information exchange, respectively. Functional status, cognitive function and mental status, and impairments are among the clinical domains of required data.
The Act requires:
Reporting of standardized patient assessment data through commonly used PAC assessment instruments:
Minimum Data Set (MDS) for SNFs
Inpatient Rehabilitation Facility – Patient Assessment Information (IRF – PAI) for IRFs
LTCH Continuity Assessment Record and Evaluation (CARE) Data Set (LCDS) for LTCHs
Outcome and Assessment Information Set (OASIS) for HHAs
Implementation of data elements specified in each domain using standardized data elements to be nested within the assessment instruments currently required for submission by LTCH, IRF, SNF, and HHA providers.
Data to be standardized and interoperable to allow exchange of data between PAC providers, among others, using common standards and definitions to provide access to longitudinal information and facilitate coordinated care.
Scope Limitations
This IG provides a framework for the exchange of observations relevant to post-acute care and other settings. It seeks to enable exchange of this information and in so doing, to promote its use in clinical care and caregiving. Consistent with this focus, it does not seek to limit or make specific recommendations on either clinical practice itself or the way that software systems display or collect information. Specifically:
The specific codes contained within example or domain-specific value sets do not constitute an endorsement or recommendation for the use of the approaches to data collection that the codes represent, whether formal assessments, clinical tests, or otherwise. Healthcare providers and other caregivers should ascertain which information is relevant for patient care and related activities, such as reimbursement. To enable interoperability across software systems using this IG, codes representing the observations made in practice should be added to the domain-specific value sets in this IG using the process described on the domains page.
This IG does not provide guidance on how to organize or display information exchanged for use by healthcare providers and caregivers. These details are critical to enabling the use of data exchanged using this IG and are an active topic of discussion within the PACIO community. However, they are outside the scope of FHIR IGs and are left to implementers who are in the best position to respond to the needs of their users and make the information available in their software in a consistent and well-integrated manner.
How to read this Guide
This IG is divided into several sections that are listed at the top of each page in the menu bar.
Home: The home page provides the introduction and background information to set context for the use of the HL7® FHIR Personal Functioning and Engagement IG.
Guidance: These pages provide overall guidance in using the profiles and transactions defined in this guide.
Formal Specification: Information about conformance to the IG, including Must Support requirements.
Use Cases: Detailed scenarios in which the Personal Functioning and Engagement IG could be used.
Structured Data Capture: Guidance on how to use structured data capture techniques to represent and use data covered by this IG.
Security: General security requirements and recommendations for Personal Functioning and Engagement IG actors, including authentication, authorization, and logging requirements and guidance.
Underlying Technologies: Information about the terminologies, notations, and design principles, specific to FHIR, that this specification uses.
Domain Support: This page provides details on the use of domain-based value sets within the IG, including how codes are assigned to a specific value set.
FHIR Artifacts: These sections provide detailed descriptions and formal definitions for all the FHIR objects defined in this IG.
Capability Statement: This artifact defines the specific capabilities that different types of systems are expected to have in order to comply with this IG. Systems conforming to this IG are expected to declare conformance with this capability statement.
Profiles: This section lists the set of Profiles defined in this IG to exchange functioning information. Each linked Profile page includes a narrative introduction and a formal definition.
Extensions: This section lists the set of Extensions defined in and used by the Profiles in this IG . Each linked Extension page includes a formal definition.
Value Sets: This section lists the value sets this IG defines.
Code Systems: This section lists the code systems this IG defines.
Examples: This section lists example instances associated with this IG.
Downloads: This page provides links to downloadable artifacts.
Globals Profiles
There are no Global profiles defined
Package Dependencies
IG
Package
FHIR
Comment
PACIO Personal Functioning and Engagement Implementation Guide
This IG defines the global extensions - the ones defined for everyone. These extensions are always in scope wherever FHIR is being used (built Sun, Mar 26, 2023 08:46+1100+11:00)
Package hl7.fhir.uv.bulkdata#2.0.0
FHIR based approach for exporting large data sets from a FHIR server to a client application (built Fri, Nov 26, 2021 05:56+1100+11:00)
Package hl7.fhir.r4.examples#4.0.1
Example resources in the R4 version of the FHIR standard
Package hl7.fhir.uv.sdc#3.0.0
The SDC specification provides an infrastructure to standardize the capture and expanded use of patient-level data collected within an EHR. This includes two components: * Support more sophisticated questionnaire/form use-cases such as those needed for research, oncology, pathology and other clinical domains. *Support pre-population and auto-population of EHR data into forms/questionnaires for uses outside direct clinical care (patient safety, adverse event reporting, public health reporting, etc.). (built Tue, Mar 8, 2022 18:32+0000+00:00)
Package hl7.fhir.us.core#5.0.1
The US Core Implementation Guide is based on FHIR Version R4 and defines the minimum conformance requirements for accessing patient data. The Argonaut pilot implementations, ONC 2015 Edition Common Clinical Data Set (CCDS), and ONC U.S. Core Data for Interoperability (USCDI) v1 provided the requirements for this guide. The prior Argonaut search and vocabulary requirements, based on FHIR DSTU2, are updated in this guide to support FHIR Version R4. This guide was used as the basis for further testing and guidance by the Argonaut Project Team to provide additional content and guidance specific to Data Query Access for purpose of ONC Certification testing. These profiles are the foundation for future US Realm FHIR implementation guides. In addition to Argonaut, they are used by DAF-Research, QI-Core, and CIMI. Under the guidance of HL7 and the HL7 US Realm Steering Committee, the content will expand in future versions to meet the needs specific to the US Realm.
These requirements were originally developed, balloted, and published in FHIR DSTU2 as part of the Office of the National Coordinator for Health Information Technology (ONC) sponsored Data Access Framework (DAF) project. For more information on how DAF became US Core see the US Core change notes. (built Wed, Jun 22, 2022 19:44+0000+00:00)
The UCUM codes, UCUM table (regardless of format), and UCUM Specification are copyright 1999-2009, Regenstrief Institute, Inc. and the Unified Codes for Units of Measures (UCUM) Organization. All rights reserved. https://ucum.org/trac/wiki/TermsOfUse
This material contains content that is copyright of SNOMED International. Implementers of these specifications must have the appropriate SNOMED CT Affiliate license - for more information contact https://www.snomed.org/get-snomed or info@snomed.org.
PACIO Personal Functioning and Engagement Implementation Guide
|
Propose a change