spelled out name of the IHE Profile
0.0.1-current - ci-build
spelled out name of the IHE Profile, published by IHE IT Infrastructure 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/supplement-template/ and changes regularly. See the Directory of published versions
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.
The Client [ITI-Y] transaction passes a go Request from a Client to a Server.
Table 2:3.YY.2-1: Actor Roles</p>
|Actor | Role |
|-------------------+--------------------------|
| [Client](volume-1.html#client) | Sends query to Server |
| [Server](volume-1.html#server) | Receives the query and responds |
### Referenced Standards
- [HL7 FHIR Release 4.0](http://hl7.org/fhir/R4/)
### 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](CapabilityStatement-IHE.ToDo.client.html)
* Requirements CapabilityStatement for [Server](CapabilityStatement-IHE.ToDo.server.html)
### Security Considerations
See [MHD Security Considerations](volume-1.html#security-considerations)
#### Security Audit Considerations
''TODO: The security audit criteria ''
##### Client Audit
When grouped with ATNA Secure Application or Secure Node the Actor shall be able to record...
''TODO: the specifics, leveraging BALP''
##### Server Audit
When grouped with ATNA Secure Application or Secure Node the Actor shall be able to record...
''TODO: the specifics, leveraging BALP''