PACIO Functional Status Implementation Guide
0.1.0 - STU Ballot

This page is part of the PACIO Functional Status Implementation Guide (v0.1.0: STU 1 Ballot 1) based on FHIR R4. The current version which supercedes this version is 1.0.0. For a full list of available versions, see the Directory of published versions

Artifacts Summary

Contents:

This page provides a list of the FHIR artifacts defined as part of this implementation guide.

Behavior: Capability Statements

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 complying with the 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.

Structures: Resource Profiles

These define constraints on FHIR resources that need to be complied with by conformant implementations

Bundled Functional Status

An point in time bundle of functional status observations for a patient.
Functional Status

An exchange of functional status data for a patient.
PACIO Questionnaire Response

A completed, or sections of a completed, CMS PAC assessment.
Prior Level Of Function

An exchange of prior level of function data for a patient.
UseOfDevice

A device used by a Patient during a functional status assessment.

Structures: Extension Definitions

These define constraints on FHIR data types that need to be complied with by conformant implementations

AssistanceRequired

Associated functional status used for display purposes.
DevicePatientUsed

A device used by a patient during a functional status assessment.

Example: Example Instances

These are example instances that show what data produced and consumed by systems conforming with this implementation guide might look like

BFS-Hospital-Discharge-Mobility-1

Sample Data
BFS-Hospital-Discharge-Mobility-1-Ob-Question-56

Sample Data
BFS-Hospital-Discharge-Mobility-1-UseOfDevice-1

Sample Data
BFS-Hospital-Discharge-Mobility-1-UseOfDevice-2

Sample Data
BFS-Hospital-Discharge-Mobility-1-UseOfDevice-3

Sample Data
BFS-Hospital-Discharge-Mobility-1-UseOfDevice-4

Sample Data
BFS-Hospital-Discharge-Mobility-1-UseOfDevice-5

Sample Data
BSJ-Diagnosis1

Sample Data
BSJ-Diagnosis2

Sample Data
BSJ-Diagnosis3

Sample Data
BSJ-Diagnosis4

Sample Data
BSJ-Diagnosis5

Sample Data
BSJ-Diagnosis6

Sample Data
BSJ-Diagnosis7

Sample Data
BSJ-Diagnosis8

Sample Data
BSJ-Diagnosis9

Sample Data
BSJ-Prior-Level-Of-Function-1

Sample Data
CMS-Device-1

Sample Data
CMS-Device-2

Sample Data
CMS-Device-3

Sample Data
CMS-Device-4

Sample Data
CMS-Device-5

Sample Data
CMS-Device-6

Sample Data
CMS-Device-7

Sample Data
Org-01

Sample Data
Org-02

Sample Data
Org-03

Sample Data
Org-Loc-01

Sample Data
Org-Loc-02

Sample Data
Org-Loc-03

Sample Data
Practitioner-DanielGranger

Sample Data
Practitioner-HoneyJones

Sample Data
Practitioner-JenCadbury

Sample Data
Practitioner-JennyGlass

Sample Data
Practitioner-JohnSmith

Sample Data
Practitioner-LunaBaskins

Sample Data
Practitioner-NoraOlogist

Sample Data
Practitioner-RonBurgendy

Sample Data
Practitioner-RonMarble

Sample Data
Practitioner-SallySmith

Sample Data
Practitioner-ScottDumble

Sample Data
QResponse-Hospital-Discharge-Mobility-1

Sample Data
Role-OT

Sample Data
Role-PT

Sample Data
Role-RN

Sample Data
patientBSJ1

Sample Data
provider-org-01

Sample Data
provider-org-loc-01

Sample Data
provider-role-pcp

Sample Data