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 Data Receiver Capability Statement

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

This example CapabilityStatement defines the expected capabilities of the Data Receiver actor when conforming to the MedMorph RA IG. The actor is responsible for defining Knowledge Artifacts, receiving reports, and submitting responses back to health care organizations. The specific knowlege artifacts, reports and responses to be supported by the Data Receiver will be defined by the Content IGs.

Raw OpenAPI-Swagger Definition file | Download

## DataReceiver

(Requirements Definition Capability Statement)

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

Published by: HL7 International - Public Health Work Group

This example CapabilityStatement defines the expected capabilities of the Data Receiver actor when conforming to the MedMorph RA IG. The actor is responsible for defining Knowledge Artifacts, receiving public health reports, and submitting responses back to health care organizations. The specific knowledge artifacts, reports, and responses supported by the Data Receiver will be defined by the content IGs.

## General

FHIR Version: | 4.0.1
Supported formats: | json

## REST behavior

The primary focus of the Data Receiver is to define Knowledge Artifacts, receive reports and submit responses back to clinical care organizations.

Security:

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

In addition the Data Receiver 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
--- | --- | --- | --- | --- | --- | --- | --- | ---
PlanDefinition (Profile) | SHALL | SHALL | SHOULD |  |  | SHALL | SHALL |

### FHIR Operations summary

The following FHIR operations SHALL be supported by the Data Receiver.

- Bundle process-message

  An example implementation of the process-message operation can be found at Example process-message operation using HAPI

### PlanDefinition

Profile: http://hl7.org/fhir/us/medmorph/StructureDefinition/us-ph-plandefinition

#### Interactions

Name | Description
--- | ---
search-type | Allows discovery of existing PlanDefinition instances representing Knowledge Artifacts.
read | Allows retrieval of a specific PlanDefinition instance.
vread | Allows retrieval of a historical version of a PlanDefinition instance.
create | Allows creation of PlanDefinition instances
update | Allows Update of PlanDefinition instances

#### Search

Parameter | Type | Definition & Chaining
--- | --- | ---
identifier | token | Search using identifiers as allowed according to the FHIR specification.
name | string | Search using PlanDefinition name.
publisher | string | Search using publisher name.
title | string | Search using title.
version | string | Search using version.
name and version | string, string | Search using name and version.