Mobile Aggregate Data Exchange, published by IHE QRPH Technical Committee. This guide is not an authorized publication; it is the continuous build for version 0.0.1-current built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/IHE/QRPH.mADX/ and changes regularly. See the Directory of published versions

2:3.YY Transaction one [Domain-YY]

This section corresponds to transaction [ITI-Y] of the IHE Technical Framework. Transaction [ITI-Y] is used by the Client and Server Actors. The go [ITI-Y] transaction is used to query and get back results.

Scope

The Client [ITI-Y] transaction passes a go Request from a Client to a Server.

Actors Roles

Table: Actor Roles

Actor	Role
Client	Sends query to Server
Server	Receives the query and responds

Referenced Standards

• HL7 FHIR Release 4.0

Interactions

Figure X.X.X.X-X: Go Interactions

go Query Message

This message uses the HTTP GET method on the target Server endpoint to convey the query parameters FHIR query.

Trigger Events

'’TODO: define the triggers’’

Message Semantics

'’TODO: define the message – usually with a StructureDefintion’’

Expected Actions

'’TODO: define expected actions’’

Go Response Message

Trigger Events

'’TODO: define the triggers’’

Message Semantics

'’TODO: define the message – usually with a StructureDefintion’’

Expected Actions

'’TODO: define expected actions’’

CapabilityStatement Resource

Server implementing this transaction shall provide a CapabilityStatement Resource as described in ITI TF-2x: Appendix Z.3 indicating the transaction has been implemented.

• Requirements CapabilityStatement for Client
• Requirements CapabilityStatement for Server

Security Considerations

See MHD Security Considerations

Security Audit Considerations

'’TODO: The security audit criteria ‘’

Client Audit

'’TODO: the specifics’’

Server Audit

'’TODO: the specifics’’