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 in its permanent home (it will always be available at this URL). For a full list of available versions, see the Directory of published versions
: Health Data Exchange App (HDEA) Server Application - (MedMorph backend services app) - JSON Representation
Raw json | Download
{
"resourceType" : "CapabilityStatement",
"id" : "medmorph-healthdata-exchange-app-server",
"text" : {
"status" : "generated",
"div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\">\n <h2>Health Data Exchange App (HDEA) Server Application - (MedMorph backend services app)</h2>\n <p>(Requirements Definition Capability Statement)</p>\n <p>Canonical URL: http://hl7.org/fhir/us/medmorph/CapabilityStatement/medmorph-healthdata-exchange-app-server</p>\n <p>Published by: <b>HL7 International - Public Health Work Group</b>\n </p>\n <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. \n This actor is responsible for receiving responses from Data Receivers and interacting with the Data Sources to create FHIR Resources. </p>\n <h2>General</h2>\n <div class=\"table-wrapper\">\n <table>\n <tbody>\n <tr>\n <th>FHIR Version:</th>\n <td>4.0.1</td>\n </tr>\n <tr>\n <th>Supported formats:</th>\n <td>json</td>\n </tr>\n </tbody>\n </table>\n </div>\n <h2>REST behavior</h2>\n <p>The primary focus of the HDEA in a Server mode is to receive responses from the Data Receivers using FHIR Messaging.</p>\n <p>\n <b>Security:</b>\n </p>\n <p>Implementations must meet the general security requirements documented in FHIR <a href=\"http://hl7.org/fhir/security.html\">Security guidance</a>.</p>\n <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>\n\t<h3>FHIR Operations summary</h3>\n <p>The HDEA SHALL implement the following operations to receive messages from Data Receivers using FHIR Messaging.</p>\n \n <ul>\n <li>\n <a href=\"http://hl7.org/fhir/OperationDefinition/MessageHeader-process-message\">process-message</a>\n </li>\n </ul>\n <br/>\n \n </div>"
},
"url" : "http://hl7.org/fhir/us/medmorph/CapabilityStatement/medmorph-healthdata-exchange-app-server",
"version" : "1.0.0",
"name" : "HealthDataExchangeAppServerMode",
"title" : "Health Data Exchange App (HDEA) Server Application - (MedMorph backend services app)",
"status" : "draft",
"date" : "2020-12-06",
"publisher" : "HL7 International - Public Health Work Group",
"contact" : [
{
"telecom" : [
{
"system" : "url",
"value" : "http://hl7.org/Special/committees/pher"
}
]
}
],
"description" : "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" : "urn:iso:std:iso:3166",
"code" : "US"
}
]
}
],
"kind" : "requirements",
"fhirVersion" : "4.0.1",
"format" : [
"json"
],
"rest" : [
{
"mode" : "server",
"documentation" : "The focus of the HDEA as a Server is to expose $process-message endpoint at the root of the FHIR server.",
"security" : {
"description" : "Implementations must meet the general security requirements documented in the security section of the implementation guide."
},
"operation" : [
{
"name" : "process-message",
"definition" : "http://hl7.org/fhir/OperationDefinition/MessageHeader-process-message"
}
]
}
]
}