Improvements to endpoints.

Author: dvribeira

docs/endpoints.md

@@ -29,11 +29,11 @@ This page lists the different endpoints available to use the e-medication servic
 
 | Transaction | Path | Comment |
 | --- | --- | --- |
-| [Provide Document Bundle (ITI-65)](transactions/iti65.md)|`/pmp/fhir`|MHD equivalent to [ITI-41](transactions/iti41.md).|
+| [Provide Document Bundle (ITI-65)](transactions/iti65.md)|`/pmp/fhir/Bundle`|MHD equivalent to [ITI-41](transactions/iti41.md).|
 | [Find Document References (ITI-67)](transactions/iti67.md)|`/pmp/fhir/DocumentReference`|MHD equivalent to [ITI-18](transactions/iti18.md).|
 | [Retrieve Document (ITI-68)](transactions/iti68.md)|`/pmp/mhd/iti68`|MHD equivalent to [ITI-43](transactions/iti43.md).|
 | [Update Document Metadata (CH:MHD-1)](transactions/chmhd1.md) | `/pmp/fhir/DocumentReference` |MHD equivalent to [ITI-57](transactions/iti57.md).|
-| [CH:PHARM-5](transactions/chpharm5.md)|`/pmp/fhir/DocumentReference/`|MHD equivalent to [CH:PHARM-1](transactions/chpharm1.md).|
+| [CH:PHARM-5](transactions/chpharm5.md)|`/pmp/fhir/DocumentReference/<operation>`|MHD equivalent to [CH:PHARM-1](transactions/chpharm1.md). The endpoint changes depending on the CH:PHARM-5 operation, see the [transaction page](transactions/chpharm5.md) for details.|
 
 ## PIXm EndPoints
 |Transaction|Path|Comment|
@@ -45,5 +45,5 @@ This page lists the different endpoints available to use the e-medication servic
 | Transaction | Path | Documentation |
 | --- | --- | --- |
 | Record Audit Event (syslog) | `:6514` | [ITI-20](transactions/iti20.md) |
-| Record Audit Event (RESTful) | `/alpage/fhir` | [ITI-20](transactions/iti20.md) | 
+| Record Audit Event (RESTful) | `/alpage/fhir/AuditEvent` | [ITI-20](transactions/iti20.md) | 
 | Audit Trail Consumption (CH:ATC) | `/alpage/fhir/AuditEvent` | [CH:ATC](transactions/chatc.md) |

docs/transactions/chpharm1.md

@@ -6,7 +6,7 @@ The eMedication service doesn't support CMA (Community Medication Administration
 
 ## Stored queries
 
-In relatio to IHE's PHARM-1, CH:PHARM-1 defines three additional queries: `FindMedicationCard`, `FindPrescriptionsForValidation` and `FindPrescriptionsForDispense`.
+In relation to IHE's PHARM-1, CH:PHARM-1 defines three additional queries: `FindMedicationCard`, `FindPrescriptionsForValidation` and `FindPrescriptionsForDispense`.
 
 ## Common query parameters
 

docs/transactions/chpharm5.md

@@ -4,6 +4,19 @@ This transaction is the RESTful alternative to the [CH:PHARM-1](chpharm1.html) t
 
 As for the [ITI-67](iti67.html) 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](https://profiles.ihe.net/ITI/IUA/#342-iua-actor-options), which means that the authorization token conveyed with the HTTP request must be an XUA token.