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
: Example MedMorph Data Source CapabilityStatement - XML Representation
Raw xml | Download
<CapabilityStatement xmlns="http://hl7.org/fhir">
<id value="medmorph-data-source"/>
<text>
<status value="generated"/>
<div xmlns="http://www.w3.org/1999/xhtml">
<h2>EHR</h2>
<p>(Requirements Definition Capability Statement)</p>
<p>Canonical URL: http://hl7.org/fhir/us/medmorph/CapabilityStatement/medmorph-data-source</p>
<p>Published by: <b>HL7 International - Public Health Work Group</b>
</p>
<p>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.</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 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.
</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 Data Source actor 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>Resource summary</h3>
<div class="table-wrapper">
<table class="grid">
<thead>
<tr>
<th>Resource</th>
<th>Search</th>
<th>Read</th>
<th>Read Version</th>
<th>Instance History</th>
<th>Resource History</th>
<th>Create</th>
<th>Update</th>
<th>Delete</th>
</tr>
</thead>
<tbody>
<tr>
<th>US Core APIs</th>
<td>
<a href="#USCore-search-type" title="Allows search of a specific US Core Resource instances.">SHALL</a>
</td>
<td>
<a href="#USCore-read" title="Allows retrieval of a specific US Core Resource instances.">SHALL</a>
</td>
<td>
</td>
<td>
</td>
<td>
</td>
<td>
</td>
<td>
</td>
<td>
</td>
</tr>
<tr>
<th>DocumentReference</th>
<td>
</td>
<td>
</td>
<td>
</td>
<td>
</td>
<td>
</td>
<td>
<a href="#DocumentReference-create" title="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.">SHOULD</a>
</td>
<td>
</td>
<td/>
</tr>
</tbody>
</table>
</div>
<h3>FHIR Operations summary</h3>
<p>The following FHIR operations SHALL be supported by the EHR.</p>
<ul>
<li>
<a>None</a>
</li>
</ul>
<br/>
<br/>
<h3>
<a href="http://hl7.org/fhir/R4/documentreference.html">DocumentReference</a>
</h3>
<p>Profile: None
</p>
<h4>Interactions</h4>
<div class="table-wrapper">
<table class="list">
<thead>
<tr>
<th>Name</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<th>
<a name="DocumentReference-create"> </a>
<span>create</span>
</th>
<td>
<p>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.</p>
</td>
</tr>
</tbody>
</table>
</div>
<br/>
<br/>
<h3>
<a href="http://hl7.org/fhir/us/core">US Core APIs</a>
</h3>
<p>Profile: None
</p>
<h4>Interactions</h4>
<div class="table-wrapper">
<table class="list">
<thead>
<tr>
<th>Name</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<th>
<a name="USCore-search-type"> </a>
<span>search</span>
</th>
<td>
<p>Allows searching of specific US Core resource profile instances.</p>
</td>
</tr>
<tr>
<th>
<a name="USCore-read"> </a>
<span>read</span>
</th>
<td>
<p>Allows retrieval of specific US Core resource profile instances</p>
</td>
</tr>
</tbody>
</table>
</div>
<br/>
<br/>
</div>
</text>
<url
value="http://hl7.org/fhir/us/medmorph/CapabilityStatement/medmorph-data-source"/>
<version value="1.0.0"/>
<name value="MedMorphDataSource"/>
<title value="Example MedMorph Data Source CapabilityStatement"/>
<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 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."/>
<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 Data Source is to allow creation, modification and deletion of Subscriptions and allows searching and retrieval of resources using US Core APIs. "/>
<security>
<description
value="Implementations must meet the general security requirements documented in the security section of the implementation guide."/>
</security>
<resource>
<type value="DocumentReference"/>
<interaction>
<extension
url="http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation">
<valueCode value="SHOULD"/>
</extension>
<code value="create"/>
<documentation
value="Allows creation of a specific DocumentReference instance."/>
</interaction>
</resource>
</rest>
</CapabilityStatement>
|
Propose a change