Query for Existing Data for Mobile (QEDm)

supports queries for clinical data elements, including observations, allergy and intolerances, conditions, diagnostic results, medications, immunizations, procedures, encounters and provenance by making the information widely available to other systems within and across enterprises.

Summary

The Query for Existing Data for Mobile Profile (QEDm) supports queries for clinical data elements, including observations, allergy and intolerances, conditions, diagnostic results, medications, immunizations, procedures, encounters and provenance by making the information widely available to other systems within and across enterprises. It defines a transaction used to query a list of specific data elements, persisted as FHIR resources.

It’s functionally equivalent to the QED Profile, but is conceived to be implemented by applications specific to mobile devices. The term “mobile” should be considered in a wider sense: it identifies not only mobile applications, but the whole class of systems that are resource- and platform-constrained. (e.g., tablets, smartphones, and embedded devices including home-health devices, but also larger systems where needs are simple, such as pulling the latest summary for display).

Benefits

.

Details

.

Systems Affected

• systems needing data-elements
• HIE Infrastructure that can extract data-elements from Documents in a Document Sharing infrastructure

Actors & Transactions:

• The Clinical Data Source in this profile responds to FHIR-based queries for one or more fine-grained data elements (FHIR resources) defined by the options listed in Section X.2. The Clinical Data Source shall support at least one of those options and may support more than one option.
• The Clinical Data Consumer in this profile sends FHIR-based queries to the Clinical Data Source for one or more fine-grained data elements (FHIR resources) defined by the options listed in Section X.2. Rendering or further processing of the data is not defined by this profile. The Clinical Data Consumer shall support querying for at least one of the data elements that are defined by this profile’s options.

Specification

Profile Status: Trial Implementation

Documents:

The supplement for Trial Implementation is not yet published

Additional Supplements: Appendix Z on HL7 FHIR

Underlying Standards:

• HL7 FHIR http://hl7.org/fhir
• RFC2616 IETF Hypertext Transfer Protocol – HTTP/1.1
• RFC3986 IETF Uniform Resource Identifier (URI): Generic Syntax
• RFC4627 The application/json Media Type for JavaScript Object Notation (JSON)
• RFC6585 IETF Additional HTTP Status Codes
• RFC4287 The Atom Syndication Format

This page is based on the Profile Overview Template