Access the MIM. The EPS uses the HL7v3 standard and current version of the MIM is v4.2.00, and yes, that’s correct, published way back in 2006. Jump to the “Medication Management” domain to see the EPS interactions and messages.
Please read the MIM in conjunction with the relevant EPS compliance specification. Some messaging requirements defined in the MIM are clarified within the EPS specification, especially with respect to the population of optional data attributes. HL7v3 schema’s are quite loose. A schema compliant message may not be an EPS compliant message.
Note. The following HL7v3 interactions are not implemented. Do not waste you time developing against any of these.
6.14 Dispense Notification with Claim Information – PORX_IN220102UK31
6.16 Dispense Reimbursement Claim Reject – PORX_IN150101UK31
6.17 Reimbursement Claim Resubmit – PORX_IN090102UK31
6.20 Forward Withdraw Notification – PORX_IN530101UK31
6.22 PSIS Cancellation Notification – PORX_IN000001UK01
Other than those above, you then work out which HL7v3 interactions you need to implement. The MIM interaction diagrams use the terms ‘Prescribing System’ and ‘Dispensing System’.
GP prescribing systems will also need to be fully Spine Demographics (known as “PDS” within the MIM) compliant to manage a patient’s demographic record. Dispensing systems may need to do that in the future but right now only need to be able to manage a patient’s nominated dispenser information, held within Spine Demographics, so need to implement the Demographics “PDS Trace Query”, “PDS Retrieval Query” and “PDS General Update Request” interactions plus their relevant response interactions.