Query for Existing Data for Mobile (QEDm)
3.0.0 - Trial-Implementation International flag

This page is part of the Query for Existing Data for Mobile (QEDm) (v3.0.0: Publication) based on FHIR (HL7® FHIR® Standard) R4. This is the current published version. For a full list of available versions, see the Directory of published versions

Artifacts Summary

Contents:

This page provides a list of the FHIR artifacts defined as part of this implementation guide.

Behavior: Capability Statements

The following artifacts define the specific capabilities that different types of systems are expected to have in order to comply with this implementation guide. Systems conforming to this implementation guide are expected to declare conformance to one or more of the following capability statements.

IHE QEDm Clinical Data Consumer Actor

CapabilityStatement for Clinical Data Consumer Actor

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 8.2 QEDm Actor Options. Rendering or further processing of the data is not defined by this profile.
IHE QEDm Clinical Data Source Actor

CapabilityStatement for Clinical Data Source Actor.

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 8.2 QEDm Actor Options.

Structures: Resource Profiles

These define constraints on FHIR resources for systems conforming to this implementation guide.

Audit Event for QEDm Query at Consumer

Defines constraints on the AuditEvent (AuditMessage) Resource for a Clinical Data Consumer to record when it performs a Clinical Data Query PCC-44.

  • Build off of the IHE BasicAudit Query event
  • add the PCC-44 as a subtype
  • client is Clinical Data Consumer
  • server is Clinical Data Source
  • entity slice for query are REQUIRED
  • entity slice for transaction is available
  • entity for patient SHALL be used
  • source is the client
Audit Event for QEDm Query at Source

Defines constraints on the AuditEvent (AuditMessage) Resource when a Clinical Data Source responds to a Clinical Data Query PCC-44.

  • Build off of the IHE BasicAudit Query event
  • add the PCC-44 as a subtype
  • client is Clinical Data Consumer
  • server is Clinical Data Source
  • entity slice for query are REQUIRED
  • entity slice for transaction is available
  • entity for patient SHALL be used
  • source is the server

Example: Example Instances

These are example instances that show what data produced and consumed by systems conforming with this implementation guide might look like.

Audit Example of PCC-44 at Consumer

Audit Event for QEDm Query Transaction by the Patient Identifier Cross-reference Consumer

where the Query was executed with a GET as follows:

GET https://server.example.com/fhir/AllergyIntolerance?patient=ex-patient
Accept: application/fhir+json; fhirVersion=4.0
Audit Example of PCC-44 at Source

Audit Event for QEDm Query Transaction by the Patient Identifier Cross-reference Source

where the Query was executed with a GET as follows:

GET https://server.example.com/fhir/AllergyIntolerance?patient=ex-patient
Accept: application/fhir+json; fhirVersion=4.0
Dummy Device example

Dummy Device example for completeness sake. No actual use of this resource other than an example target
Dummy DocumentReference example

Dummy DocumentReference example for completeness sake. No actual use of this resource other than an example target
Example Encounter

holding typical values
Example Patient

The patient from which all the example relate
Example of a search set bundle

Search on Weight Observations with reverse include requesting Provenance. This is returning two weight Observations and one Provenance.
Example of an IHE QEDm blood pressure R4 observation, minimal

holding typical values
Example of an QEDm bodyWeight R4 observation

Sample for demonstration purposes of a common weight Observation

  • marked as compliant with IHE.QEDm.bodyWeight profile
  • marked as test data
  • status of final
  • category vital-signs
  • code of loinc body weight
  • subject of the example patient
  • effective time of December 25th, 2004
  • weight 185 pounds
  • note: a bit heavy
Example of an QEDm bodyWeight R4 observation

Sample for demonstration purposes of a common weight Observation

  • marked as compliant with IHE.QEDm.bodyWeight profile
  • marked as test data
  • status of final
  • category vital-signs
  • code of loinc body weight
  • subject of the example patient
  • effective time of December 25th, 2004
  • weight 185 pounds
  • note: a bit heavy
Provenance of extracted resources

Sample of a Provenance of a set of target FHIR Resource elements derived from a DocumentReference