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

This page is part of the HRSA Uniform Data System (UDS) Patient Level Submission (PLS) (UDS+ or uds-plus) FHIR IG (v1.0.1: STU1) based on FHIR (HL7® FHIR® Standard) R4. The current version which supersedes this version is 2.0.0. For a full list of available versions, see the Directory of published versions

Resource Profile: De-Identified UDS Plus Procedure

Official URL: http://fhir.org/guides/hrsa/uds-plus/StructureDefinition/uds-plus-procedure Version: 1.0.1
Standards status: Trial-use Maturity Level: 2 Computable Name: UDSPlusProcedure

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

Introduction

This profile is used to represent de-identified Procedure 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 Procedure.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 Procedure resource text element may contain information such as the Procedure 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 Procedure resource id should not be included in the De-identified Procedure 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 Procedure. All resource references to the Procedure 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

  • performedDateTime
  • extension.recordedDate

Usage:

Formal Views of Profile Content

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

This structure is derived from Procedure

NameFlagsCard.TypeDescription & Constraintsdoco
.. Procedure 0..*ProcedureDe-Identified UDS Plus Procedure
... id S0..1idThe de-identified Procedure identifier created by the health center to send data to UDS+ Data Receiver
... text 0..0
... contained 0..0
... status S1..1codepreparation | in-progress | not-done | on-hold | stopped | completed | entered-in-error | unknown
... statusReason S0..1CodeableConceptReason for current status
... code S1..1CodeableConceptIdentification of the procedure
Binding: US Core Procedure Codes (extensible): The set of codes indicating the procedures

... subject S1..1Reference(De-Identified UDS Plus Patient)Who the procedure was performed on
... encounter S0..1Reference(De-Identified UDS Plus Encounter)Encounter created as part of
... performed[x] S0..1dateTime, Period, string, Age, RangeWhen the procedure was performed
... performer S0..*BackboneElementThe people who performed the procedure
... bodySite S0..*CodeableConceptTarget body sites

doco Documentation for this format

Terminology Bindings (Differential)

PathConformanceValueSet
Procedure.codeextensibleUSCoreProcedureCodes

 

Other representations of profile: CSV, Excel, Schematron