This page is part of the US Medication REMS (v1.0.0-ballot: STU1 Ballot 1) based on FHIR (HL7® FHIR® Standard) R4. . For a full list of available versions, see the Directory of published versions
This page provides a list of the FHIR artifacts defined as part of this implementation guide.
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 conforming to this implementation guide are expected to declare conformance to one or more of the following capability statements.
Medication REMS Capability Statement - Provider System |
This CapabilityStatement describes the expected capabilities of a Provider System that conforms to the conventions of the Medication REMS FHIR implementation guide. |
Medication REMS Capability Statement - REMS Administrator System |
This CapabilityStatement describes the expected capabilities of a REMS Administrator System that conforms to the conventions of the Medication REMS FHIR implementation guide. |
These define constraints on FHIR resources for systems conforming to this implementation guide.
Medication REMS Task - SMART Launch |
This profile defines a Task to be returned in a REMS Administrator’s CDS Hooks response - enabling the provider or staff to launch a SMART app from their work queue. |
These are example instances that show what data produced and consumed by systems conforming with this implementation guide might look like.
example-patient-123 |
Example of a US Core patient |
example-rems-docref-1 |
Example of a US Core document reference containing a patient’s REMS program information |
medication-rems-task-smart-launch-1 |
Complete patient enrollment using the DRUG-X REMS SMART app |