Specific FHIR data elements
There are a number of feasible application architectures that would support ePMA to Pharmacy interoperability, and wider interoperability with shared record platforms.
With regard to the use of the specific FHIR data elements, the architectures may change how and when the
status elements are used.
identifier is the most important element of a FHIR resource for interoperability. It acts as the externally facing unique business identifier for the resource. A key phrase from the FHIR R4 standard is;
identifier] ...All resources that have an identifier element support searching by the identifier, so that records can be located by that method.
By contrast, the resource
id is normally an internally facing unique logical identifier. Within the FHIR R4 standard is the key phrase related to the logical
id where it is:
id] ...assigned by the server responsible for storing it
The different types of business
MedicationDispense resources made visible within systems may change depending the interoperability architecture. Within some architectures, only valid end-states may be exposed, e.g.
MedicationRequests. Within other architectures, when systems query the system acting as the FHIR server, records or any state may be returned, including records that may be
draft or other values that denote the business process has not yet completed.