Making Electronic Data More available for Research and Public Health (MedMorph)
1.0.0 - STU 1

Making Electronic Data More available for Research and Public Health (MedMorph), published by HL7 International - Public Health Work Group. This is not an authorized publication; it is the continuous build for version 1.0.0). This version is based on the current content of https://github.com/HL7/fhir-medmorph/ and changes regularly. See the Directory of published versions

## CapabilityStatement: Example MedMorph Data Source CapabilityStatement

Official URL: http://hl7.org/fhir/us/medmorph/CapabilityStatement/medmorph-data-source | Version: 1.0.0
Draft as of 2020-12-06 | Computable Name: MedMorphDataSource

This is an example CapabilityStatement that defines the expected capabilities of the Data Source actor. This CapabilityStatement is an example for Content IG creators on how to create a capability statement for a Data Source actor.

Raw OpenAPI-Swagger Definition file | Download

## EHR

(Requirements Definition Capability Statement)

Canonical URL: http://hl7.org/fhir/us/medmorph/CapabilityStatement/medmorph-data-source

Published by: HL7 International - Public Health Work Group

This is an example CapabilityStatement that defines the expected capabilities of the Data Source actor. This CapabilityStatement is an example for Content IG creators on how to create a capability statement for a Data Source actor.

## General

FHIR Version: | 4.0.1
Supported formats: | json

## REST behavior

The primary focus of the Data Source is to notify subscribers based on subscriptions or other events and support US Core APIs when implementing MedMorph RA and its Content IGs. This capability statement is an example and an actual Data Source CapabilityStatement will be defined for each use case in its Content IG. This is present here to guide the Content IG creators on how to create a Data Source CapabilityStatement.

Security:

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

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

### Resource summary

Resource | Search | Read | Read Version | Instance History | Resource History | Create | Update | Delete
--- | --- | --- | --- | --- | --- | --- | --- | ---
US Core APIs | SHALL | SHALL |  |  |  |  |  |
DocumentReference |  |  |  |  |  | SHOULD |  |

### FHIR Operations summary

The following FHIR operations SHALL be supported by the EHR.

- None

### DocumentReference

Profile: None

#### Interactions

Name | Description
--- | ---
create | Allows creation of a specific DocumentReference Resource instance used by the Backend Services App to post the response back to the EHR.The attachment will contain the response bundle received from the TTP/PHA.

### US Core APIs

Profile: None

#### Interactions

Name | Description
--- | ---
search | Allows searching of specific US Core resource profile instances.
read | Allows retrieval of specific US Core resource profile instances