HRSA 2023 Uniform Data System (UDS) Patient Level Submission (PLS) (UDS+) FHIR IG
1.0.0 - STU1 Release 1 - Standard for Trial-Use
HRSA 2023 Uniform Data System (UDS) Patient Level Submission (PLS) (UDS+) FHIR IG
1.0.0 - STU1 Release 1 - Standard for Trial-Use
HRSA 2023 Uniform Data System (UDS) Patient Level Submission (PLS) (UDS+) FHIR IG - Local Development build (v1.0.0). See the Directory of published versions
| Official URL: http://hl7.org/fhir/us/uds-plus/CapabilityStatement/uds-plus-data-submitter-client | Version: 1.0.0 | |||
| Standards status: Trial-use | Maturity Level: 2 | Computable Name: UdsPlusDataSubmitter | ||
This is a CapabilityStatement that defines the expected capabilities of the Data Submitter actor.
Raw OpenAPI-Swagger Definition file | Download
(Requirements Definition Capability Statement)
Canonical URL: http://hl7.org/fhir/us/uds-plus/CapabilityStatement/uds-plus-data-submitter-client
Published by: HL7 International - Public Health Work Group
This is a CapabilityStatement that defines the expected capabilities of the Data Submitter actor as a client.
| FHIR Version: | 4.0.1 |
|---|---|
| Supported formats: | json |
The primary focus of the Data Submitter actor as a client is to invoke the Group/$export operation identified below and extract the UDS+ data using US Core and QI Core profiles. In certain cases, the Data Submitter MAY have to invoke individual patient api's to extract the necessary UDS+ data when the Data Source does not support Group/$export operation. data.
Security:
Implementations must meet the general security requirements documented in FHIR Security guidance.
In addition the Data Submitter actor as a client needs to meet the security requirements as outlined in the SMART on FHIR Backend Services Authorization
| Resource | Search | Read | Read Version | Instance History | Resource History | Create | Update | Delete |
|---|---|---|---|---|---|---|---|---|
| US Core data APIs and Data elements | SHALL | SHALL | ||||||
| QI Core data APIs and Data elements | SHALL | SHALL |
As a client, the Data Submitter has to be capable of invoking the below operation on the Data Source.
As a client, the Data Submitter has to be capable of invoking the below operation on the Data Receiver to submit the manifest file.
Profiles: All US Core profiles
| Name | Description |
|---|---|
| search |
Search for specific US Core resource profile instances. |
| read |
Retrieve specific US Core resource profile instances |
Profiles: All QI Core profiles