Making Electronic Data More available for Research and Public Health (MedMorph)
1.0.0 - STU 1 United States of America flag

This page is part of the Making EHR Data MOre available for Research and Public Health (MedMorph) (v1.0.0: STU1 Release 1) based on FHIR R4. This is the current published version. For a full list of available versions, see the Directory of published versions

CapabilityStatement: Health Data Exchange App (HDEA) Server Application - (MedMorph backend services app)

Official URL: http://hl7.org/fhir/us/medmorph/CapabilityStatement/medmorph-healthdata-exchange-app-server Version: 1.0.0
Draft as of 2020-12-06 Computable Name: HealthDataExchangeAppServerMode

This CapabilityStatement defines the expected capabilities of the HDEA actor when conforming to the MedMorph RA IG and playing the role of a server that receives messages from Data Receivers using FHIR Messaging.

Raw OpenAPI-Swagger Definition file | Download

Health Data Exchange App (HDEA) Server Application - (MedMorph backend services app)

(Requirements Definition Capability Statement)

Canonical URL: http://hl7.org/fhir/us/medmorph/CapabilityStatement/medmorph-healthdata-exchange-app-server

Published by: HL7 International - Public Health Work Group

This CapabilityStatement defines the expected capabilities of the HDEA actor when conforming to the MedMorph IG and acting as a server implementing FHIR messaging operations. This actor is responsible for receiving responses from Data Receivers and interacting with the Data Sources to create FHIR Resources.

General

FHIR Version: 4.0.1
Supported formats: json

REST behavior

The primary focus of the HDEA in a Server mode is to receive responses from the Data Receivers using FHIR Messaging.

Security:

Implementations must meet the general security requirements documented in FHIR Security guidance.

In addition the HDEA needs to meet the security requirements as outlined in the Formal Specification - Security Section.

FHIR Operations summary

The HDEA SHALL implement the following operations to receive messages from Data Receivers using FHIR Messaging.