Scenarios
Customer workflows for using the FHIR resources, interactions, and search parameters advertised by DDFS.
Use these scenarios to plan common device-data and clinical-data workflows. Before sending requests, retrieve the CapabilityStatement for the API version that your application will use and confirm that it advertises every required resource, interaction, operation, and search parameter.
Use an OAuth 2.0 access token issued by OCI Identity Domains with the DDFS resource scopes required for each request. Configure the client and obtain tokens by following Create an Integrated Application and DDFS Authentication Reference.
These scenarios illustrate customer application workflows. Adapt resource content to the FHIR version, profiles, terminology, and data-governance requirements selected for your application.
Working with FHIR Resources
- Scenario: Access Device and Patient Data
- Scenario: Search the Device Registry and Associations
- Scenario: Search Vital Signs and Laboratory Results
- Scenario: Manage the Specimen Lifecycle
- Scenario: Manage the ServiceRequest Lifecycle
- Scenario: Search the PractitionerRole Directory
- Scenario: Search the Organization Directory
- Scenario: Search the Endpoint Registry
- Scenario: Delete, Purge Deleted, and Hard Delete
Connected Clinical Workflows
The following examples use FHIR R4 4.0.1 resources. Choose the resources you need from the R4 resource catalog, then follow their operation pages for request requirements and supported searches. Use the same patient reference where the records concern the same person, and supply the resource references needed by your application. A shared patient reference provides context; it does not create a link between every record automatically.
Medication Records and Measurements
A monitoring application can display a patient's medication information alongside device measurements.
| Resource | Role in the application |
|---|---|
| Medication | Describe a medication product. A MedicationRequest or MedicationStatement can identify it through medicationReference, or describe the medication directly with medicationCodeableConcept. |
| MedicationRequest | Record the order or request and its instructions for the patient. |
| MedicationStatement | Record a statement about the patient's medication use. This is a separate record from the order. |
| Observation | Record measurements that the application displays alongside the medication information. See vital signs and laboratory results. |
Your application selects and presents the relevant records. Storing a MedicationRequest does not transmit a prescription to a pharmacy, dispense or administer medication, or determine whether a patient has taken it.
Care Plans and Care Teams
A care coordination application can present a patient's plan, the people involved and the clinical information used to follow progress.
| Resource | Role in the application |
|---|---|
| CarePlan | Describe the plan and intended activities for the patient. |
| CareTeam | Identify care participants. Use the related Practitioner, PractitionerRole and Organization records when needed. |
| Condition and Observation | Record the health concerns and measurements that the application presents with the plan. |
Your application manages assignments, notifications and activity execution. Storing a CarePlan or CareTeam does not schedule care, assign tasks or notify participants automatically.
Clinical Documents and Device Observations
An application can present clinical reports and document references alongside a patient's device readings.
| Resource | Role in the application |
|---|---|
| Device and Observation | Identify the device and record its measurements. See vital signs and laboratory results for the measurement workflow. |
| DiagnosticReport | Record a report and its references to supporting observations. |
| DocumentReference | Store document metadata and attachment content or locations supplied by the application. DDFS does not retrieve attachment URLs or process document contents. |
| Composition | Organize clinical content into an authored document structure. A standalone Composition does not constitute a FHIR document Bundle. |
Your application retrieves the relevant records and assembles the display or document. DDFS does not generate clinical documents or extract observations from document contents automatically. Follow each resource's supported search parameters; a resource reference does not imply support for additional chained searches or _include options.
Coordinate Resource Requests
When one resource must reference another resource that you create, create the referenced resource first and use its returned ID in the subsequent request. Configure the required scopes for every resource used by the application, and follow the scope matrix and each operation's authorization requirements.
Use separate ordered requests for dependent writes. The supported batch interaction handles independent entries and does not provide an atomic transaction across these records.