This transaction is used to issue parameterized queries that result in a list of Document Reference resources.
                            

This transaction is used to get documents.
                            

This transaction is used to locate and return metadata for previously stored document submission sets or folders.
                            

Performs a query against a patient identifier cross-reference manager using HTTP, REST, and JSON/XML message encoding
                            

This transaction is used by the Alert Reporter to query an Alert Aggregator for alert status information as communicated to an Alert Aggregator for a particular alert. 
                            

This transaction is used by the Alert Reporter to report alerts to the Alert Aggregator.  The Alert Reporter sends alerts to the Alert Aggregator actor in an unsolicited manner. 
                            

Evaluates an order against guidelines and/or policies to determine its appropriateness in a given context.
                            

Displays the CDS questionnaire using HTML web pages and returns the result invoker
                            

The delivery of an audit event description from any secure node to the Audit Repository.
                            

Retrieve Audit Records. Search ATNA audit records based upon queries using ATNA audit record content.
                            

Retrieve Syslog Messages. Search syslog messages based upon using the syslog metadata.
                            

Transfer Multiple Events delivers syslog messages in bulk as a single RESTful transaction. The payload format is the same as for Retrieve Syslog Message [ITI-82].
                            

This transaction allows a File Source to publish a file and related metadata, or to update an existing file. 
                            

This transaction allows a File Source to update file metadata. 
                            

This transaction allows a File Consumer to query for a file metadata that meets certain criteria 
                            

Performs a query against a patient demographics supplier using HTTP, REST, and JSON/XML message encoding.
                            

This transaction uses RESTful API to query clinical data elements and retrieve them as sets of FHIR resources.

The Mobile Query Existing Data transaction is used to query for clinical fine grained data elements that satisfy a set of parameters by using the FHIR framework. The result of the query is a FHIR Bundle containing FHIR clinical data Resources that match the query parameters.

The QEDm Profile assumes that categories and codes referenced by these FHIR Resources need to be defined at the time of deployment. The specification of these FHIR Resources make recommendations on categories and codes that should be considered.



                            

The Data Consumer retrieves death reporting related health information from the Data responder. 

The Data Consumer is responsible for creating a FHIR-based request for death reporting related health information and retrieving this information from the Data responder.

The Data Responder responds to the request for death reporting related health information or provides the appropriate response if the information does not exist. 

VRDR (DEC 2019): This transaction supports queries for Death Reporting information.
                            

Retrieve Document Set