HRSA 2024 Uniform Data System (UDS) Patient Level Submission (PLS) (UDS+) FHIR IG
2.0.0 - STU2 Release 1 - Standard for Trial-Use
HRSA 2024 Uniform Data System (UDS) Patient Level Submission (PLS) (UDS+) FHIR IG
2.0.0 - STU2 Release 1 - Standard for Trial-Use
HRSA 2024 Uniform Data System (UDS) Patient Level Submission (PLS) (UDS+) FHIR IG, published by HRSA BPHC. This guide is not an authorized publication; it is the continuous build for version 2.0.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/drajer-health/uds-plus/ and changes regularly. See the Directory of published versions
| Page standards status: Trial-use | Maturity Level: 2 |
<CapabilityStatement xmlns="http://hl7.org/fhir">
<id value="uds-plus-data-receiver-server"/>
<text>
<status value="generated"/>
<div xmlns="http://www.w3.org/1999/xhtml">
<h2>Data Receiver</h2>
<p>(Requirements Definition Capability Statement)</p>
<p>Canonical URL: http://fhir.org/guides/hrsa/uds-plus/CapabilityStatement/uds-plus-data-receiver-server</p>
<p>Published by: <b>HL7 International - Public Health Work Group</b>
</p>
<p>This is a CapabilityStatement that defines the expected capabilities of the Data Receiver Server 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 Receiver as a Server is to receive the manifest which contains the links to the UDS+ data that has
been extracted by the health center and is being made available to HRSA.
</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 Receiver actor needs to meet the security requirements as outlined in the <a href="spec.html#smart-on-fhir-backend-services-authorization">SMART on FHIR Backend Services Authorization</a></p>
<h3>FHIR Operations summary</h3>
<p>The following FHIR operations SHALL be supported by the Data Source.</p>
<ul>
<li>
<a href="OperationDefinition-import.html">UDS+ Import Operation</a>
</li>
<li>
<a href="https://hl7.org/fhir/uv/bulkdata/export.html#bulk-data-status-request">Status Polling using Content-Location received for Bulk Data Import as part of the Content-Location HTTP Header</a>
</li>
</ul>
<br/>
<br/>
</div>
</text>
<url
value="http://fhir.org/guides/hrsa/uds-plus/CapabilityStatement/uds-plus-data-receiver-server"/>
<version value="2.0.0"/>
<name value="UdsPlusDataReceiverServer"/>
<title value="Uds Plus Data Receiver CapabilityStatement"/>
<status value="draft"/>
<date value="2020-12-06"/>
<publisher value="HRSA BPHC"/>
<contact>
<telecom>
<system value="url"/>
<value value="https://bphc.hrsa.gov/"/>
</telecom>
</contact>
<description
value="This is a CapabilityStatement that defines the expected capabilities of the Data Receiver actor as a Server."/>
<jurisdiction>
<coding>
<system value="http://unstats.un.org/unsd/methods/m49/m49.htm"/>
<code value="001"/>
</coding>
</jurisdiction>
<kind value="requirements"/>
<fhirVersion value="4.0.1"/>
<format value="json"/>
<rest>
<mode value="server"/>
<documentation
value="The primary focus of the Data Receiver as a Server is to receive the notification manifest which contains the links to the UDS+ data that has been extracted by the health center and is being made available to HRSA."/>
<security>
<description
value="Implementations must meet the general security requirements documented in the security section of the implementation guide."/>
</security>
<operation>
<name value="import"/>
<definition
value="http://fhir.org/guides/hrsa/uds-plus/OperationDefinition/import"/>
</operation>
</rest>
</CapabilityStatement>