1. HealthIT.gov
  • Print

Interoperability Need: Data Element Based Query for Clinical Health Information


Interoperability Need: Data Element Based Query for Clinical Health Information

Interoperability Need: Data Element Based Query for Clinical Health Information

Type

Standard/Implementation Specification

Standards Process Maturity

Implementation Maturity

Adoption Level

Federally Required

Cost

Test Tool Availability

Standard

Fast Healthcare Interoperability Resources (FHIR), DSTU 2

Balloted Draft

Pilot

 rating 1

No

Free

No

Emerging Standard

HL7 FHIR STU 3

In Development

Pilot

N/A

No

Free

No
Limitations, Dependencies, and Preconditions for Consideration: Applicable Security Patterns for Consideration:
  • System Authentication -   The information and process necessary to authenticate the systems involved
  • User Details - identifies the end user who is accessing the data
  • User Role – identifies the role asserted by the individual initiating the transaction.
  • Purpose of Use - Identifies the purpose for the transaction.
  • Patient Consent Information - Identifies the patient consent information that may be required before data can be accessed.
    • May be required to authorize any exchange of patient information
    • May be required to authorized access and use of patient information
    • May be required to be sent along with disclosed patient information to
    • advise the receiver about policies to which end users must comply
  • Security Labeling – the health information is labeled with security metadata necessary for access control by the end user.
  • Query Request ID - Query requesting application assigns a unique identifier for each query request in order to match the response to the original query.
Matthew Greene
Department of Veterans Affairs

Instead of referencing simply “HL7 FHIR STU 3”, it would be useful to reference the “DataElement” resource applicable to this requirement.