Physical Activity Implementation Guide
1.0.0 - STU Release 1 United States of America flag

This page is part of the U.S. Physical Activity IG (v1.0.0: STU 1.0) 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

ExampleScenario: Scenario 1 - Exercise Prescription

Official URL: http://hl7.org/fhir/us/physical-activity/ExampleScenario/Scen1ExercisePrescriptionScenario Version: 1.0.0
Standards status: Informative Computable Name: ExercisePrescription

This scenario provides an example of the types of data exchanges that are described in the Exercise Prescription scenario from the Scenarios page.

The scenario shows the flows of information between the different systems and the various FHIR calls involved, as well as what the data might have looked like in each of the exchanges. There are detailed tables below that provide details on each of the steps in the exchange as well as the types of data being shared. From the instances table, it's possible to navigate to sample XML and JSON instances.

Actors

NameTypeDescription
Patient AppSystem

A patient app used to query resources related to the exercise plan

EHRSystem

EHR that records patient's exercise plan

Diagram

ExercisePrescriptionPatient AppPatient AppEHREHRDay after appointmentdetailsQuery CarePlan(payload)response(payload)Query Goal(payload)response(payload)Query ServiceRequest(payload)response(payload)A couple of weeks laterdetailsPost days/week(payload)Post minutes/day(payload)Post minutes/week(payload)Post stength days/week(payload)A little more than 6 months after first appointmentdetailsQuery revised CarePlan(payload)response(payload)Query revised Goal(payload)response(payload)Query ServiceRequest(payload)response(payload)

Processes

Process: Day after appointment

The patient accesses the care plan, goals and exercise prescription made available on the EHR

Pre-conditions:

Encounter (and other supporting) resources created

Post-conditions:

Patient app has retrieved exercise plan related resources

StepNameDescriptionInitatorReceiverRequestResponse
1Query CarePlan - search-type

Patient app queries exercise CarePlan describing proposed exercise regime.

Patient AppEHRQuery for patient physical activity care plansInitial care plan search response bundle
2Query Goal - search-type

Patient app queries Goals (100 minutes/week).

Patient AppEHRQuery for patient physical activity goalsInitial goal search response bundle
3Query ServiceRequest - search-type

Patient app queries ServiceRequest (order for ‘exercise’).

Patient AppEHRQuery for patient exercise prescriptions and referralsSearch result of exercise prescriptions and referrals
Process: A couple of weeks later

The exchange noted here would actually occur many times (though not necessarily regularly). Only a single set of data is shown for simplicity.

Pre-conditions:

Patient app is able to write records to EHR

Post-conditions:

EHR has weekly activity level observations

StepNameDescriptionInitatorReceiverRequestResponse
5Post days/week - create

Patient app posts average days per week of moderate-to-vigorous physical activity. POST https://goodhealth.example.org/fhir/Observation

Patient AppEHRExample physical activity days per week record
6Post minutes/day - create

Patient app posts average minutes per day of moderate-to-vigorous physical activity. POST https://goodhealth.example.org/fhir/Observation

Patient AppEHRExample physical activity minutes per day record
7Post minutes/week - create

Patient app posts average minutes per week of moderate-to-vigorous physical activity. POST https://goodhealth.example.org/fhir/Observation

Patient AppEHRExample physical activity minutes per week record
8Post stength days/week - create

Patient app posts average days per week of muscle-strengthening physical activity. POST https://goodhealth.example.org/fhir/Observation

Patient AppEHRExample strength days per week record
Process: A little more than 6 months after first appointment

In practice, the patient app would likely check for new CarePlans and Goals each time it launches. However, this is the first time there'd be something new to retrieve.

Pre-conditions:

CarePlan and Goal have been updated in EHR

Post-conditions:

Patient app retrieves updated CarePlan and Goal

StepNameDescriptionInitatorReceiverRequestResponse
9Query revised CarePlan - search-type

Patient app queries revised CarePlan with providers notes.

Patient AppEHRQuery for patient physical activity care plansSecond care plan search response bundle
10Query revised Goal - search-type

Patient app queries new Goals.

Patient AppEHRQuery for patient physical activity goalsSecond goal search response bundle
11Query ServiceRequest - search-type

The results of this search are the same as the initial call because the exercise 'prescription' has not changed.

Patient AppEHRQuery for patient exercise prescriptions and referralsSearch result of exercise prescriptions and referrals

Instances

NameTypeContentDescription
Query for patient physical activity care plansBinary

Query for CarePlans for a patient: GET https://goodhealth.example.org/fhir/CarePlan?patient=Patient/Scen1PatientKhatun&status=active,on-hold&category=http%3A//hl7.org/fhir/us/physical-activity/CodeSystem/pa-temporary-codes|PhysicalActivity

Query for patient physical activity goalsBinary

Query for Goals for a patient: GET https://goodhealth.example.org/fhir/Goal?patient=Patient/Scen1PatientKhatun&status=active,on-hold,completed&category=http%3A//hl7.org/fhir/us/physical-activity/CodeSystem/pa-temporary-codes|PhysicalActivity

Query for patient exercise prescriptions and referralsBinary

Query for ServiceRequests for a patient: GET https://goodhealth.example.org/fhir/ServiceRequest?patient=Patient/Scen1PatientKhatun&status=active,on-hold&category=http%3A//hl7.org/fhir/us/physical-activity/CodeSystem/pa-temporary-codes|PhysicalActivity

Patient physical activity care planCarePlan

CarePlan describing proposed exercise regime

  • Initial CarePlan
here

CarePlan describing proposed exercise regime

  • Updated CarePlan
here

CarePlan describing proposed exercise regime

Physical Activity weekly targetGoal

Goal indicating target number of minutes/week of moderate-vigorous physical activity

  • Initial goal
here

Goal indicating target number of minutes/week of moderate-vigorous physical activity

  • Initial goal
here

Goal indicating target number of minutes/week of moderate-vigorous physical activity

Updated goalBundlehere

Updated value of 150 mins/week

Initial care plan search response bundleBundlehere

Only contains 1 plan, though in practice, more than one is possible

Contains: Initial CarePlan
Second care plan search response bundleBundlehere

In a real system, the id would be the same as the original

Contains: Updated CarePlan
Initial goal search response bundleBundlehere

There could be multiple goals, but in the scenario there's only one.

Contains: Initial goal
Second goal search response bundleBundlehere

In a real system, the id would be the same as the original

Contains: Updated goal
Prescription for exerciseServiceRequesthere

Expressed as a ServiceRequest with performer of the patient

Search result of exercise prescriptions and referralsBundlehere

There could be a mix of an exercise prescription plus referrals, but in this case there's only the prescription.

Contains: Prescription for exercise
Example physical activity days per week recordObservationhere

Average days per week of moderate-to-vigorous physical activity.

Example physical activity minutes per day recordObservationhere

Average minutes per day of moderate-to-vigorous physical activity.

Example physical activity minutes per week recordObservationhere

Average minutes per week of moderate-to-vigorous physical activity.

Example strength days per week recordObservationhere

Average days per week of muscle-strengthening physical activity.