CH:PHARM-5

This transaction is the RESTful alternative to the CH:PHARM-1 transaction, as defined by the defined by IHE Pharmacy in the CMPD profile but with some Swiss extensions. The same business logic and constraints as for CH:PHARM-1 applies.

As for the ITI-67 request, the eMedication service backend is grouped with the XDS on FHIR option, and hence the identifier query parameter is not supported. All other parameters specified by PHARM-5 are supported.

Endpoints

Each CH:PHARM-1 stored query becomes a FHIR operation in CH:PHARM-5. This means that, unlike its XDS-like counterpart, CH:PHARM-5 has a distinct endpoint per defined operation. These are the names of the operations: - $find-medication-treatment-plans - $find-prescritions - $find-dispenses - $find-prescriptions-for-validation - $find-prescriptions-for-dispense - $find-medication-list - $find-medication-card

In practice, this means that if the base URL for FHIR DocumentReference resources is https://example.com/pmp/fhir/DocumentReference, then the endpoint for a CH:PHARM-5 FindMedicationCard request would be https://example.com/pmp/fhir/DocumentReference/$find-medication-card.

Security Considerations

Note that beside the security considerations expressed (directly or indirectly) by parent profiles, the eMedication service implementation supports only, for now, the SAML Token option, which means that the authorization token conveyed with the HTTP request must be an XUA token.