HRSA 2023 Uniform Data System (UDS) Patient Level Submission (PLS) (UDS+) FHIR IG
1.0.0 - STU1 Release 1 - Standard for Trial-Use International flag

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

Resource Profile: De-Identified UDS Plus ServiceRequest

Official URL: http://hl7.org/fhir/us/uds-plus/StructureDefinition/uds-plus-servicerequest Version: 1.0.0
Standards status: Trial-use Maturity Level: 2 Computable Name: UDSPlusServiceRequest

The UDS+ profile is based on the ServiceRequest resource and establishes the core elements, extensions, vocabularies and value sets for representing ServiceRequest for UDS+ program.

All canonical (Official) URLs will be changed in the future and are not available currently on the web.

Introduction

This profile is used to represent de-identified ServiceRequest information. The de-identification process has to remove all data elements not explicitly identified as “SUPPORTED” in the profile.

The HHS De-identification Guidance is to be followed to ensure appropriate level of de-identification is performed.

According to the HHS guidance, dates should not have a precision of more than the year. This means month and day cannot be included. This includes ServiceRequest.occurenceDateTime.

In FHIR Resources, text elements and reference.display elements which provide human readable information to the providers may be generated using programs and tools from the data present within the resource. For e.g a ServiceRequest resource text element may contain information such as the ServiceRequest date, patient information. This type of information will enable identification of the individuals. In order to avoid inadvertent revealing of PII/PHI, text elements cannot be included in the De-identified FHIR resource and the submission will be rejected when text elements are present by the validation process.

Ids and References

The original ServiceRequest resource id should not be included in the De-identified ServiceRequest instance. Instead a new id should be created and provided as part of the FHIR resource. The Data Submitter should be capable of using the generated id to relink the data to the original ServiceRequest. All resource references to the ServiceRequest submitted as part of the UDS+ report should refer to newly generated id.

Resource references cannot contain text element as it may contain PHI/PII. The text element for following references are not allowed

  • subject
  • encounter

Date Truncation

The Data Submitter has to truncate the following dates to only have a precision of year

  • authoredOn

Usage:

Formal Views of Profile Content

Description of Profiles, Differentials, Snapshots and how the different presentations work.

This structure is derived from ServiceRequest

NameFlagsCard.TypeDescription & Constraintsdoco
.. ServiceRequest 0..*ServiceRequestDe-Identified UDS Plus ServiceRequest
... id S0..1idThe de-identified ServiceRequest identifier created by the health center to send data to UDS+ Data Receiver
... text 0..0
... contained 0..0
... intent S1..1codeproposal | plan | directive | order | original-order | reflex-order | filler-order | instance-order | option
... doNotPerform S1..1booleanTrue if service/procedure should not be performed
... code S1..1CodeableConceptWhat is being requested/ordered
Binding: US Core Procedure Codes (extensible): The set of codes indicating the ServiceRequests

... subject S1..1Reference(De-Identified UDS Plus Patient)Individual or Entity the service is ordered for
... encounter S0..1Reference(De-Identified UDS Plus Encounter)Encounter in which the request was created
... occurrence[x] S0..1dateTime, Period, TimingWhen service should occur
... authoredOn S0..1dateTimeDate request signed
... requester S0..1Reference(Practitioner | PractitionerRole | Organization | Patient | RelatedPerson | Device)Who/what is requesting service
... bodySite S0..*CodeableConceptLocation on Body

doco Documentation for this format

Terminology Bindings (Differential)

PathConformanceValueSet
ServiceRequest.codeextensibleUSCoreProcedureCodes

 

Other representations of profile: CSV, Excel, Schematron