1. Medication Statement Event Query RMIM

2. Simple Query Implemented using query parameter in the GET URI – (section URI)/?(queryParameter)=(value) – http://…/medications/?encounterId=… Prevents complex queries – Very simple to implement – Complex queries are can be modeled alternative approach

3. Query Representation in hData REST Map query to an HTTP POST to the resource URL of the section – Provide “Medication Statement Event Query” in initial request to resource URL – Set the confirmation URL to a temporary URL within the section, e.g. (section)/queryResult- (UUID) – Provide query result as Atom feed at confirmation URL

4. Metadata for Query What metadata (beyond identity of sender) is required to be sent with the query – This should be informed by ControlAct RMIM for queries IHE IT TF metadata model – Should be represented either in hData metadata and/or additional data sent with the query

5. Discussion Benefits – REST compliant approach that integrates neatly into overall approach using feeds to represents lists – Flexible, and implementable with minimal effort – Can be made privacy aware by limiting results Issues – Should take generalized approach – May require small changes to OMG REST spec

6. Wire-level Simplification Strategy Use capability for alternate representations of data for multi-representational approach Required & Default: – HL7 V3 XML-ITS representation of medication statement data model Optional & Selectable: – “Greened” representation, using the green_c32_medications.xsd schema from the informal greenCDA ballot package – FHIR representation, based on upcoming FHIR Pharmacy project