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
: Health Data Exchange App (HDEA) Server Application - (MedMorph backend services app) - XML Representation
Raw xml | Download
<CapabilityStatement xmlns="http://hl7.org/fhir">
<id value="medmorph-healthdata-exchange-app-server"/>
<text>
<status value="generated"/>
<div xmlns="http://www.w3.org/1999/xhtml">
<h2>Health Data Exchange App (HDEA) Server Application - (MedMorph backend services app)</h2>
<p>(Requirements Definition Capability Statement)</p>
<p>Canonical URL: http://hl7.org/fhir/us/medmorph/CapabilityStatement/medmorph-healthdata-exchange-app-server</p>
<p>Published by: <b>HL7 International - Public Health Work Group</b>
</p>
<p>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. </p>
<h2>General</h2>
<div class="table-wrapper">
<table>
<tbody>
<tr>
<th>FHIR Version:</th>
<td>4.0.1</td>
</tr>
<tr>
<th>Supported formats:</th>
<td>json</td>
</tr>
</tbody>
</table>
</div>
<h2>REST behavior</h2>
<p>The primary focus of the HDEA in a Server mode is to receive responses from the Data Receivers using FHIR Messaging.</p>
<p>
<b>Security:</b>
</p>
<p>Implementations must meet the general security requirements documented in FHIR <a href="http://hl7.org/fhir/security.html">Security guidance</a>.</p>
<p>In addition the HDEA needs to meet the security requirements as outlined in the <a href="spec.html#authentication-and-authorization-requirements">Formal Specification - Security Section.</a></p>
<h3>FHIR Operations summary</h3>
<p>The HDEA SHALL implement the following operations to receive messages from Data Receivers using FHIR Messaging.</p>
<ul>
<li>
<a href="http://hl7.org/fhir/OperationDefinition/MessageHeader-process-message">process-message</a>
</li>
</ul>
<br/>
</div>
</text>
<url
value="http://hl7.org/fhir/us/medmorph/CapabilityStatement/medmorph-healthdata-exchange-app-server"/>
<version value="1.0.0"/>
<name value="HealthDataExchangeAppServerMode"/>
<title
value="Health Data Exchange App (HDEA) Server Application - (MedMorph backend services app)"/>
<status value="draft"/>
<date value="2020-12-06"/>
<publisher value="HL7 International - Public Health Work Group"/>
<contact>
<telecom>
<system value="url"/>
<value value="http://hl7.org/Special/committees/pher"/>
</telecom>
</contact>
<description
value="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."/>
<jurisdiction>
<coding>
<system value="urn:iso:std:iso:3166"/>
<code value="US"/>
</coding>
</jurisdiction>
<kind value="requirements"/>
<fhirVersion value="4.0.1"/>
<format value="json"/>
<rest>
<mode value="server"/>
<documentation
value="The focus of the HDEA as a Server is to expose $process-message endpoint at the root of the FHIR server."/>
<security>
<description
value="Implementations must meet the general security requirements documented in the security section of the implementation guide."/>
</security>
<operation>
<name value="process-message"/>
<definition
value="http://hl7.org/fhir/OperationDefinition/MessageHeader-process-message"/>
</operation>
</rest>
</CapabilityStatement>