Consumer Mobile Health Application Functional Framework, Release 2
2.0.1 - CI build International flag

Consumer Mobile Health Application Functional Framework, Release 2, published by HL7 International / Mobile Health. This guide is not an authorized publication; it is the continuous build for version 2.0.1 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/cmhaff-ig/ and changes regularly. See the Directory of published versions

Requirements: APU.6 Data Exchange and Interoperability (Function)

Official URL: http://hl7.org/ehrs/uv/cmhaffr2/Requirements/CMHAFFR2-APU.6 Version: 2.0.1
Standards status: Informative Computable Name: APU_6_Data_Exchange_and_Interoperability

This category applies only if an app exchanges data with other devices, health apps, and/or HIT systems. If so, there are applicable standards for data format, vocabulary, and transport, to increase interoperability and ease of connection.

Description I:

Related Regulations and Standards: • Direct Project Applicability Statement for Secure Health Transport https://www.healthit.gov/policy-researchers-implementers/direct-project • HL7 Consolidated CDA • HL7 FHIR STU. http://www.hl7.org/FHIR/index.html • SMART ON FHIR. https://smarthealthit.org/ • http://www.hl7.org/implement/standards/product_brief.cfm?product_id=379 • IEEE 10073 Personal Health Data Standards https://standards.ieee.org/develop/wg/PHD.html • “MedMij” information Exchange standards for Personal Health Environment https://www.medmij.nl (Netherlands) Includes HL7 Health Clinical Information models (HCIM), which provide context for discrete clinical data (e.g., systolic blood pressure); the standard is being used in the Netherlands.

Criteria N:
APU.6#01 SHALL conditional

IF the system exchanges discrete clinical data THEN the system SHALL use standard terminologies, such as SNOMED CT or LOINC.

APU.6#02 SHALL conditional

IF the system exchanges discrete clinical data THEN the system SHALL use standard format and content, such as HL7 FHIR, SMART on FHIR, HL7 Consolidated CDA, or Detailed Clinical Models (HL7 CIMI).

APU.6#03 SHALL conditional

IF the system exchanges AI-derived data with another device, app, repository, or HIT system THEN the system SHALL identify AI-derived information as such in the exchanged content and SHALL include available provenance, source-data, model-version, and human-review metadata so recipients can distinguish it from verified clinical observations.

APU.6#04 SHOULD conditional

IF the system exchanges discrete clinical data with devices THEN the system SHOULD use standard format and content, such as IEEE 11073.

APU.6#05 SHOULD conditional

IF the system exchanges unstructured data THEN the system SHOULD use standard or commonly accepted formats, such as HL7 CDA or PDF.

APU.6#06 SHALL conditional

IF the system exchanges AI-generated narrative or summary content THEN the system SHALL distinguish AI-generated narrative from source records and SHALL avoid transmitting the narrative as a verified clinical fact unless it has been reviewed and authenticated according to the receiving system's policy.

APU.6#07 SHOULD conditional

IF the system collects personal health information THEN the system SHOULD allow that data to be imported into or exported from the system.

APU.6#08 SHOULD conditional

IF the system exchanges AI-derived data THEN the system SHOULD use applicable interoperable provenance and annotation mechanisms, such as HL7 FHIR Provenance or a realm-appropriate equivalent, when those mechanisms are available to the receiving system.

Notes:

Direct Project Applicability Statement for Secure Health Transport https://www.healthit.gov/policy-researchers-implementers/direct-project