Generated Narrative: ExampleScenario Resource ExampleScenario "Scen2ProviderToPersonaltrainerReferral" wg: pc url: http://hl7.org/fhir/us/physical-activity/ExampleScenario/Scen2ProviderToPersonaltrainerReferral version: 1.0.1 name: ProviderToPersonalTrainerReferral status: draft date: 2024-03-12 17:26:10+0000 publisher: HL7 International / Patient Care contact: HL7 International / Patient Care: http://www.hl7.org/Special/committees/patientcare jurisdiction: United States of America (ISO 3166-1 Codes for the representation of names of countries and their subdivisions — Part 1: Country code#US) actor actorId: goodCardio type: entity name: Good Health Cardiology description: EHR that records patient's exercise plan actor actorId: getFit type: entity name: Get Fit Training description: 'Light' service provider' actor actorId: Fit4Life type: entity name: Fit 4 Life description: 'Full' service provider' actor actorId: registry type: entity name: Service Registry description: Registry of candidate service providers - outside the scope of this IG instance resourceId: Scen2query1 resourceType: Binary name: Query for personal trainers near Mrs. Johansson description: Search to retrieve list of Service Providers for personal trainers near Mrs. Johansson: `GET https://registry.example.org/fhir/PractitionerRole?role=228239008|http%3A//snomed.info/sct&location.near=37.8393|84.2700|20|[mi_us]&_include=PractitionerRole:practitioner` instance resourceId: Scen2query2 resourceType: Binary name: Query for Get Fit assigned referrals description: Query Task and associated ServiceRequest and Patient: `GET https://goodCardio.example.org/fhir/Task?status=requested&owner=https%3A//registry.example.org/fhir/Organization/Scen2OrgGetFitTraining&_include=Task:patient&_include=Task:focus` instance resourceId: Scen2query3 resourceType: Binary name: Query for Referral & Patient for retrieved Task description: Search to retrieve ServiceRequest and Patient for specified Task: `GET https://goodCardio.example.org/fhir/ServiceRequest?_id=Scen2ServiceRequest&_include=ServiceRequest:patient` instance resourceId: Scen2query4 resourceType: Binary name: Query for patient physical activity conditions description: Search to retrieve Conditions: `GET https://goodCardio.example.org/fhir/Condition?patient=Scen2PatientJohansson&category=http:%3A//hl7.org/fhir/us/physical-activity/CodeSystem/PATemporaryCodesorary-codes|PhysicalActivity` instance resourceId: Scen2query5 resourceType: Binary name: Query for patient physical activity observations description: Search to retrieve Observations: `GET https://goodCardio.example.org/fhir/Observation?patient=Scen2PatientJohansson&category=http:%3A//hl7.org/fhir/us/physical-activity/CodeSystem/PATemporaryCodesorary-codes|PhysicalActivity` instance resourceId: Scen2query6 resourceType: Binary name: Query for EHR-issued task based on notification description: Search to retrieve Task: `GET https://fit4life.example.org/fhir/Task?_id=Scen2TaskFit4Life` instance resourceId: Scen2query7 resourceType: Binary name: Query for report and referenced observations description: Search on referenced Observations: `GET https://fit4.life.example.org/fhir/DiagnosticReport?id=Scen2DiagnosticReport&_include=DiagnosticReport:result` instance Extension Definition for ExampleScenario.instance.content for Version 5.0: Patient/Scen2PatientJohansson " JOHANSSON" resourceId: Scen2PatientJohansson resourceType: Patient name: Mrs. Johansson Patient Record description: Demographics and contact information instance Extension Definition for ExampleScenario.instance.content for Version 5.0: Practitioner/Scen2PractitionerMatthews " MATTHEWS" resourceId: Scen2PractitionerMatthews resourceType: Practitioner name: Mr. Matthews Registry Entry description: Practitioner details for personal trainer Mr. Matthews instance Extension Definition for ExampleScenario.instance.content for Version 5.0: Practitioner/Scen2PractitionerWang " WANG" resourceId: Scen2PractitionerWang resourceType: Practitioner name: Ms. Wang Registry Entry description: Practitioner details for personal trainer Ms. Matthews instance Extension Definition for ExampleScenario.instance.content for Version 5.0: PractitionerRole/Scen2RoleMatthews resourceId: Scen2RoleMatthews resourceType: PractitionerRole name: Mr. Matthews Registry Entry description: Practitioner organization details for personal trainer Mr. Matthews instance Extension Definition for ExampleScenario.instance.content for Version 5.0: Practitioner/Scen2PractitionerWang " WANG" resourceId: Scen2PractitionerWang resourceType: PractitionerRole name: Ms. Wang Registry Entry description: Practitioner organization details for personal trainer Ms. Matthews instance Extension Definition for ExampleScenario.instance.content for Version 5.0: Subscription/Scen2SubscriptionEhr resourceId: Scen2SubscriptionEhr resourceType: Subscription name: Subscription from EHR description: Establishes the subscription for the EHR to monitor tasks it's created instance Extension Definition for ExampleScenario.instance.content for Version 5.0: Subscription/Scen2SubscriptionGetFit resourceId: Scen2SubscriptionGetFit resourceType: Subscription name: Subscription from Get Fit Training description: Establishes the subscription for the service provider to monitor tasks created for it instance Extension Definition for ExampleScenario.instance.content for Version 5.0: Bundle/Scen2PractitionerTrainerSearchsetBundle resourceId: Scen2PractitionerTrainerSearchsetBundle resourceType: Bundle name: Searchset Bundle returning list of personal trainers description: In practice, the set of candidates would likely be longer. Note that this functionality is outside the scope of this IG. ContainedInstances - ResourceId * Scen2PractitionerMatthews instance Extension Definition for ExampleScenario.instance.content for Version 5.0: Condition/Scen2ConditionLackOfExercise resourceId: Scen2ConditionLackOfExercise resourceType: Condition name: Low physical activity condition description: New condition added to chart instance Extension Definition for ExampleScenario.instance.content for Version 5.0: Condition/Scen2ConditionHypertension resourceId: Scen2ConditionHypertension resourceType: Condition name: Hypertension condition description: Older condition instance Extension Definition for ExampleScenario.instance.content for Version 5.0: Observation/Scen2ObsDaysPerWeek resourceId: Scen2ObsDaysPerWeek resourceType: Observation name: Initial days per week of activity description: Exercise of once per week instance Extension Definition for ExampleScenario.instance.content for Version 5.0: Observation/Scen2ObsDaysPerWeek2 resourceId: Scen2ObsDaysPerWeek2 resourceType: Observation name: New days per week of activity description: Exercising 5 times per week instance Extension Definition for ExampleScenario.instance.content for Version 5.0: Observation/Scen2ObsMinutesPerDay resourceId: Scen2ObsMinutesPerDay resourceType: Observation name: Initial minutes per day of activity description: 15 minutes per day instance Extension Definition for ExampleScenario.instance.content for Version 5.0: Observation/Scen2ObsMinutesPerDay2 resourceId: Scen2ObsMinutesPerDay2 resourceType: Observation name: New minutes per day of activity description: 32 minutes per day instance Extension Definition for ExampleScenario.instance.content for Version 5.0: Observation/Scen2ObsActivityGroup resourceId: Scen2ObsActivityGroup resourceType: Observation name: Information about a run description: Collection of sub-observations about a single run instance Extension Definition for ExampleScenario.instance.content for Version 5.0: Observation/Scen2ObsActivityType resourceId: Scen2ObsActivityType resourceType: Observation name: Type of activity - run description: Indicates that the activity performed was a run instance Extension Definition for ExampleScenario.instance.content for Version 5.0: Observation/Scen2ObsActivityDuration resourceId: Scen2ObsActivityDuration resourceType: Observation name: Duration of run description: Run was 30 minutes instance Extension Definition for ExampleScenario.instance.content for Version 5.0: Observation/Scen2ObsActivityMeanHR resourceId: Scen2ObsActivityMeanHR resourceType: Observation name: Average heart rate during run description: Average heart rate of 132 bpm instance Extension Definition for ExampleScenario.instance.content for Version 5.0: Observation/Scen2ObsActivityPeakHR resourceId: Scen2ObsActivityPeakHR resourceType: Observation name: Peak heart rate during run description: Peak heart rate of 177 bpm instance Extension Definition for ExampleScenario.instance.content for Version 5.0: Observation/Scen2ObsActivityExperience resourceId: Scen2ObsActivityExperience resourceType: Observation name: Experience of run by patient description: Experience of run was positive instance Extension Definition for ExampleScenario.instance.content for Version 5.0: Observation/Scen2ObsCalories resourceId: Scen2ObsCalories resourceType: Observation name: Calories burned during run description: 517 calories burned during run instance Extension Definition for ExampleScenario.instance.content for Version 5.0: DiagnosticReport/Scen2DiagnosticReport resourceId: Scen2DiagnosticReport resourceType: DiagnosticReport name: Report from personal trainer description: Letter to provider indicating how the consultation went instance Extension Definition for ExampleScenario.instance.content for Version 5.0: ServiceRequest/Scen2ServiceRequest resourceId: Scen2ServiceRequest resourceType: ServiceRequest name: Referral for support description: Indicates what is to be done and when - but not by whom instance resourceId: Scen2TaskGetFit resourceType: Task name: Task seeking GetFit to fulfill referral description: This is the initial Task seeking fulfillment version Extension Definition for ExampleScenario.instance.version.title for Version 5.0: Initial GetFit Task Extension Definition for ExampleScenario.instance.version.content for Version 5.0: Task/Scen2TaskGetFitV1 versionId: 1 description: Initial version of the referral fulfillment request for GetFit with a status of 'requested' version Extension Definition for ExampleScenario.instance.version.title for Version 5.0: Updated GetFit Task Extension Definition for ExampleScenario.instance.version.content for Version 5.0: Task/Scen2TaskGetFitV2 versionId: 2 description: Version of the referral fulfillment request for GetFit after it has been changed to 'rejected' instance Extension Definition for ExampleScenario.instance.content for Version 5.0: Bundle/Scen2SubscriptionNotificationNewTaskBundle resourceId: Scen2SubscriptionNotificationNewTaskBundle resourceType: Bundle name: Subscription notification indicating new Task description: Points to the initial 'requested' version of the Task instance Extension Definition for ExampleScenario.instance.content for Version 5.0: Bundle/Scen2TaskGetFitResponseBundle resourceId: Scen2TaskGetFitResponseBundle resourceType: Bundle name: Search-set Bundle returning referenced Task description: Returns Task referenced in subscription notification. Includes associated ServiceRequest and Patient ContainedInstances - ResourceId VersionId * Scen2TaskGetFit 1 instance resourceId: Scen2TaskFit4Life resourceType: Task name: Task seeking FitLife to fulfill referral description: This is the second Task seeking fulfillment (after the first was rejected) version Extension Definition for ExampleScenario.instance.version.title for Version 5.0: Initial Fit4Life Task Extension Definition for ExampleScenario.instance.version.content for Version 5.0: Task/Scen2TaskFit4LifeV1 versionId: 1 description: Initial version of the referral fulfillment request for Fit4Life with a status of 'requested' version Extension Definition for ExampleScenario.instance.version.title for Version 5.0: Updated Fit4Life Task Extension Definition for ExampleScenario.instance.version.content for Version 5.0: Task/Scen2TaskFit4LifeV2 versionId: 2 description: Version of the referral fulfillment request for Fit4Life after it has been changed to 'accepted' version Extension Definition for ExampleScenario.instance.version.title for Version 5.0: Completed Fit4Life Task Extension Definition for ExampleScenario.instance.version.content for Version 5.0: Task/Scen2TaskFit4LifeV3 versionId: 3 description: Version of the referral fulfillment request for Fit4Life after it has been changed to 'completed' and a link to the report added instance Extension Definition for ExampleScenario.instance.content for Version 5.0: Bundle/Scen2ReferralFit4LifeResponseBundle resourceId: Scen2ReferralFit4LifeResponseBundle resourceType: Bundle name: ServiceRequest search response for Fit4Life description: Search-set Bundle returning ServiceRequest and Patient for the Task posted to Fit4Life ContainedInstances - ResourceId * Scen2PatientJohansson instance Extension Definition for ExampleScenario.instance.content for Version 5.0: Bundle/Scen2TaskEHRResponseBundle1 resourceId: Scen2TaskEHRResponseBundle1 resourceType: Bundle name: Accepted Task search response for EHR description: Search-set Bundle returning 'accepted' Task with id based on subscription notification ContainedInstances - ResourceId VersionId * Scen2TaskFit4Life 2 instance Extension Definition for ExampleScenario.instance.content for Version 5.0: Bundle/Scen2TaskEHRResponseBundle2 resourceId: Scen2TaskEHRResponseBundle2 resourceType: Bundle name: Completed Task search response for EHR description: Search-set Bundle returning 'completed' Task with id based on subscription notification ContainedInstances - ResourceId VersionId * Scen2TaskFit4Life 3 instance Extension Definition for ExampleScenario.instance.content for Version 5.0: Bundle/Scen2ConditionResponseBundle resourceId: Scen2ConditionResponseBundle resourceType: Bundle name: Condition response for Fit 4 Life description: Search-set Bundle containing the patient's Conditions (that Fit 4 Life has access to) ContainedInstances - ResourceId * Scen2ConditionHypertension instance Extension Definition for ExampleScenario.instance.content for Version 5.0: Bundle/Scen2ObservationResponseBundle resourceId: Scen2ObservationResponseBundle resourceType: Bundle name: Observation response for Fit 4 Life description: Search-set Bundle containing the patient's Observations (that Fit 4 Life has access to) ContainedInstances - ResourceId * Scen2ObsMinutesPerDay instance Extension Definition for ExampleScenario.instance.content for Version 5.0: Bundle/Scen2NotificationUpdatedTaskBundle resourceId: Scen2NotificationUpdatedTaskBundle resourceType: Bundle name: Subscription Notification that Task has updated description: Pointer to the Task that has been updated instance Extension Definition for ExampleScenario.instance.content for Version 5.0: Bundle/Scen2NotificationCompletedTaskBundle resourceId: Scen2NotificationCompletedTaskBundle resourceType: Bundle name: Subscription Notification that Task has completed description: Pointer to the Task that has been updated instance Extension Definition for ExampleScenario.instance.content for Version 5.0: Bundle/Scen2DiagnosticReportObservationsResponseBundle resourceId: Scen2DiagnosticReportObservationsResponseBundle resourceType: Bundle name: DiagnosticReport response for EHR description: Search-set Bundle returning DiagnosticReport and the Observations it references ContainedInstances - ResourceId * Scen2ObsCalories process title: Subscription Establishment preConditions: Good Health Cardiology, Fit 4 Life, and Get Fit training have established legal and technical arrangements for interoperability postConditions: Subscriptions are successfully created allowing Good Health Cardiology to monitor Fit4Life-assigned Tasks and GetFit to monitor Tasks assigned to it hosted on Good Health Cardiology step operation number: 1 type: create name: Create service provider-monitoring Subscription initiator: goodCardio receiver: Fit4Life description: EHR posts Subscription to Fit 4 Life to monitor Tasks. Request: `POST https://fit4life.example.org/fhir/Subscription` Response: `201 Created` Requests - ResourceId * Scen2SubscriptionEhr step operation number: 2 type: create name: Create EHR-monitoring Subscription initiator: getFit receiver: goodCardio description: Get Fit Training posts Subscription to EHR to monitor Tasks. Request: `POST https://goodCardio.example.org/fhir/Subscription` Response: `201 Created` Requests - ResourceId * Scen2SubscriptionGetFit process title: 1 Hour after appointment preConditions: EHR has completed the appointment with the patient postConditions: EHR has retrieved list of personal trainers and notified GetFit of new Task step operation number: 3 type: search-type name: Retrieve service provider list initiator: goodCardio receiver: registry description: Search to retrieve list of Service Providers for personal trainers near Mrs. Johansson. Requests - ResourceId * Scen2query1 Responses - ResourceId * Scen2PractitionerTrainerSearchsetBundle step operation number: 4 type: create name: Subscription notification of new Task initiator: goodCardio receiver: getFit description: Service provider is notified of new Task via subscription. Request: `POST https://fit4life.example.org/fhir/Subscription` Response: `201 Created` Requests - ResourceId * Scen2SubscriptionNotificationNewTaskBundle process title: 1 Day after appointment preConditions: GetFit has received the notification of new Task postConditions: GetFit has queried Task, associated ServiceRequest and Patient; and updated Task to refused step operation number: 5 type: search-type name: Getfit retrieves referral initiator: getFit receiver: goodCardio description: GetFit retrieves the referenced Task and its associated ServiceRequest and Patient. Requests - ResourceId * Scen2query2 Responses - ResourceId * Scen2TaskGetFitResponseBundle step operation number: 6 type: update name: GetFit refuses task initiator: getFit receiver: goodCardio description: GetFit updates the Task status to 'refused' with a reason. Request: `PUT https://goodCardio.example.org/fhir/Task/Scen2TaskGetFitV1` Response: `200 Ok` Requests - ResourceId VersionId * Scen2TaskGetFit 2 process title: An Hour later preConditions: EHR has a Task seeking fulfillment of ServiceRequest for Fit4Life postConditions: Fit4Life has retrieved ServiceRequest, Patient, Conditions, Observations, and updated Task step operation number: 7 type: create name: Create Task on Fit4Life initiator: goodCardio receiver: Fit4Life description: New Task is created directly on Fit4Life's server. Request: `POST https://fit4life.example.org/fhir/Task` Response: `201 Created` Requests - ResourceId VersionId * Scen2TaskFit4Life 1 step operation number: 8 type: search-type name: Fit4Life retrieves referral initiator: Fit4Life receiver: goodCardio description: Fit4Life retrieves the ServiceRequest and Patient referenced by the Task. Requests - ResourceId * Scen2query3 Responses - ResourceId * Scen2ReferralFit4LifeResponseBundle step operation number: 9 type: search-type name: Fit4Life retrieves conditions initiator: Fit4Life receiver: goodCardio description: Fit4Life retrieves the physical-activity related Conditions associated with the patient. Requests - ResourceId * Scen2query4 Responses - ResourceId * Scen2ConditionResponseBundle step operation number: 10 type: search-type name: Fit4Life retrieves referral initiator: Fit4Life receiver: goodCardio description: Fit4Life retrieves the physical-activity related Observations associated with the patient. (In practice there would typically be more than are shown here, and some might not be for profiles defined in this IG.) Requests - ResourceId * Scen2query5 Responses - ResourceId * Scen2ObservationResponseBundle step operation number: 11 type: create name: EHR gets referral acceptance initiator: Fit4Life receiver: goodCardio description: A subscription notification to the EHR is triggered when Fit4Life changes the prescription status to 'accepted'. Request: `POST https://goodCardio.example.org/mySubscriptions` Response: `200 Ok` Requests - ResourceId * Scen2NotificationUpdatedTaskBundle step operation number: 12 type: search-type name: EHR retrieves accepted Task initiator: goodCardio receiver: Fit4Life description: EHR retrieves the Task referenced by the subscription notification Requests - ResourceId * Scen2query6 Responses - ResourceId * Scen2TaskEHRResponseBundle1 process title: 2 Months Later preConditions: Fit4Life has updated the Task postConditions: EHR has retrieved the completed Task, DiagnosticReport, and associated Observations step operation number: 13 type: create name: EHR gets referral acceptance initiator: Fit4Life receiver: goodCardio description: A subscription notification to the EHR is triggered when Fit4Life changes the Task status to 'completed'. Request: `POST https://goodCardio.example.org/mySubscriptions` Response: `200 Ok` Requests - ResourceId * Scen2NotificationCompletedTaskBundle step operation number: 14 type: search-type name: EHR retrieves completed Task initiator: goodCardio receiver: Fit4Life description: EHR retrieves the Task referenced by the subscription notification Requests - ResourceId * Scen2query6 Responses - ResourceId * Scen2TaskEHRResponseBundle2 step operation number: 15 type: search-type name: EHR retrieves report initiator: goodCardio receiver: Fit4Life description: EHR retrieves the Fit4Life DiagnosticReport using the id provided in the Task. It also uses _include to retrieve referenced observations Requests - ResourceId * Scen2query7 Responses - ResourceId * Scen2DiagnosticReportObservationsResponseBundle
EHR that records patient's exercise plan
Registry of candidate service providers - outside the scope of this IG
Query for personal trainers near Mrs. Johansson
Search to retrieve list of Service Providers for personal trainers near Mrs. Johansson: `GET https://registry.example.org/fhir/PractitionerRole?role=228239008|http%3A//snomed.info/sct&location.near=37.8393|84.2700|20|[mi_us]&_include=PractitionerRole:practitioner`
Query Task and associated ServiceRequest and Patient: `GET https://goodCardio.example.org/fhir/Task?status=requested&owner=https%3A//registry.example.org/fhir/Organization/Scen2OrgGetFitTraining&_include=Task:patient&_include=Task:focus`
Query for Referral & Patient for retrieved Task
Search to retrieve ServiceRequest and Patient for specified Task: `GET https://goodCardio.example.org/fhir/ServiceRequest?_id=Scen2ServiceRequest&_include=ServiceRequest:patient`
Query for patient physical activity conditions
Search to retrieve Conditions: `GET https://goodCardio.example.org/fhir/Condition?patient=Scen2PatientJohansson&category=http:%3A//hl7.org/fhir/us/physical-activity/CodeSystem/PATemporaryCodesorary-codes|PhysicalActivity`
Query for patient physical activity observations
Search to retrieve Observations: `GET https://goodCardio.example.org/fhir/Observation?patient=Scen2PatientJohansson&category=http:%3A//hl7.org/fhir/us/physical-activity/CodeSystem/PATemporaryCodesorary-codes|PhysicalActivity`
Query for EHR-issued task based on notification
Search to retrieve Task: `GET https://fit4life.example.org/fhir/Task?_id=Scen2TaskFit4Life`
Query for report and referenced observations
Search on referenced Observations: `GET https://fit4.life.example.org/fhir/DiagnosticReport?id=Scen2DiagnosticReport&_include=DiagnosticReport:result`
Practitioner details for personal trainer Mr. Matthews
Practitioner details for personal trainer Ms. Matthews
Practitioner organization details for personal trainer Mr. Matthews
Practitioner organization details for personal trainer Ms. Matthews
Establishes the subscription for the EHR to monitor tasks it's created
Establishes the subscription for the service provider to monitor tasks created for it
Searchset Bundle returning list of personal trainers
In practice, the set of candidates would likely be longer. Note that this functionality is outside the scope of this IG.
Collection of sub-observations about a single run
Indicates that the activity performed was a run
Letter to provider indicating how the consultation went
Indicates what is to be done and when - but not by whom
This is the initial Task seeking fulfillment
Initial version of the referral fulfillment request for GetFit with a status of 'requested'
Version of the referral fulfillment request for GetFit after it has been changed to 'rejected'
Subscription notification indicating new Task
Points to the initial 'requested' version of the Task
Search-set Bundle returning referenced Task
Returns Task referenced in subscription notification. Includes associated ServiceRequest and Patient
Task seeking FitLife to fulfill referral
This is the second Task seeking fulfillment (after the first was rejected)
Initial version of the referral fulfillment request for Fit4Life with a status of 'requested'
Version of the referral fulfillment request for Fit4Life after it has been changed to 'accepted'
Version of the referral fulfillment request for Fit4Life after it has been changed to 'completed' and a link to the report added
ServiceRequest search response for Fit4Life
Search-set Bundle returning ServiceRequest and Patient for the Task posted to Fit4Life
Search-set Bundle returning 'accepted' Task with id based on subscription notification
Search-set Bundle returning 'completed' Task with id based on subscription notification
Search-set Bundle containing the patient's Conditions (that Fit 4 Life has access to)
Search-set Bundle containing the patient's Observations (that Fit 4 Life has access to)
Subscription Notification that Task has updated
Pointer to the Task that has been updated
Subscription Notification that Task has completed
Search-set Bundle returning DiagnosticReport and the Observations it references
Good Health Cardiology, Fit 4 Life, and Get Fit training have established legal and technical arrangements for interoperability
Subscriptions are successfully created allowing Good Health Cardiology to monitor Fit4Life-assigned Tasks and GetFit to monitor Tasks assigned to it hosted on Good Health Cardiology
Create service provider-monitoring Subscription
EHR posts Subscription to Fit 4 Life to monitor Tasks. Request: `POST https://fit4life.example.org/fhir/Subscription` Response: `201 Created`
Get Fit Training posts Subscription to EHR to monitor Tasks. Request: `POST https://goodCardio.example.org/fhir/Subscription` Response: `201 Created`
EHR has completed the appointment with the patient
EHR has retrieved list of personal trainers and notified GetFit of new Task
Search to retrieve list of Service Providers for personal trainers near Mrs. Johansson.
Service provider is notified of new Task via subscription. Request: `POST https://fit4life.example.org/fhir/Subscription` Response: `201 Created`
GetFit has received the notification of new Task
GetFit has queried Task, associated ServiceRequest and Patient; and updated Task to refused
GetFit retrieves the referenced Task and its associated ServiceRequest and Patient.
GetFit updates the Task status to 'refused' with a reason. Request: `PUT https://goodCardio.example.org/fhir/Task/Scen2TaskGetFitV1` Response: `200 Ok`
EHR has a Task seeking fulfillment of ServiceRequest for Fit4Life
Fit4Life has retrieved ServiceRequest, Patient, Conditions, Observations, and updated Task
New Task is created directly on Fit4Life's server. Request: `POST https://fit4life.example.org/fhir/Task` Response: `201 Created`
Fit4Life retrieves the ServiceRequest and Patient referenced by the Task.
Fit4Life retrieves the physical-activity related Conditions associated with the patient.
Fit4Life retrieves the physical-activity related Observations associated with the patient. (In practice there would typically be more than are shown here, and some might not be for profiles defined in this IG.)
A subscription notification to the EHR is triggered when Fit4Life changes the prescription status to 'accepted'. Request: `POST https://goodCardio.example.org/mySubscriptions` Response: `200 Ok`
EHR retrieves the Task referenced by the subscription notification
EHR has retrieved the completed Task, DiagnosticReport, and associated Observations
A subscription notification to the EHR is triggered when Fit4Life changes the Task status to 'completed'. Request: `POST https://goodCardio.example.org/mySubscriptions` Response: `200 Ok`
EHR retrieves the Fit4Life DiagnosticReport using the id provided in the Task. It also uses _include to retrieve referenced observations