STU 4 (current: 'STU 3', others = 'STU 1','STU 2')
desc
STU 4 Publication
changes
changes.html
RelatedIgs
(None Found)
Proposed path for this publication should usually be the canonical with the version or sequence appended and then some kind of label (typically '-snapshot')
The release must have a mode of working, milestone, technical-correction or withdrawal
The jira specification file appears to be out of date with the versions, artifacts and pages currently defined in the IG. A proposed revised file to be reviewed and, if appropriate, submitted as a pull request against the XML folder in https://github.com/HL7/JIRA-Spec-Artifacts. To see the differences, perform a file compare on 'template/jira-current.xml' (a normalized view of what is in Github) and 'template/jira-new.xml' (reflects current IG content)
The extension http://hl7.org/fhir/StructureDefinition/operationoutcome-sourceResource could not be found so is not allowed here
Editor's Comment: 01. The tracker FHIR-57615 to add this extension to the FHIR Standard extension pack has been approved and will be applied in the next versionExtension_EXT_Unknown_NotHere
No definition could be found for URL value 'http://hl7.org/fhir/StructureDefinition/operationoutcome-sourceResource'
Editor's Comment: 01. The tracker FHIR-57615 to add this extension to the FHIR Standard extension pack has been approved and will be applied in the next versionType_Specific_Checks_DT_URL_Resolve
The extension http://hl7.org/fhir/StructureDefinition/operationoutcome-sourceResource could not be found so is not allowed here
Editor's Comment: 01. The tracker FHIR-57615 to add this extension to the FHIR Standard extension pack has been approved and will be applied in the next versionExtension_EXT_Unknown_NotHere
No definition could be found for URL value 'http://hl7.org/fhir/StructureDefinition/operationoutcome-sourceResource'
Editor's Comment: 01. The tracker FHIR-57615 to add this extension to the FHIR Standard extension pack has been approved and will be applied in the next versionType_Specific_Checks_DT_URL_Resolve
01. The tracker FHIR-57615 to add this extension to the FHIR Standard extension pack has been approved and will be applied in the next version
%No definition could be found for URL value 'http://hl7.org/fhir/StructureDefinition/operationoutcome-sourceResource'% (2 uses)
%The extension http://hl7.org/fhir/StructureDefinition/operationoutcome-sourceResource could not be found so is not allowed here% (2 uses)
02. These are examples of the Bulk Data Manifest Logical Models and not FHIR Resources
%Unable to find resourceType property% (10 uses)
03. An inline example is provided in the extension description
WARNING: StructureDefinition.where(url = 'http://hl7.org/fhir/uv/bulkdata/StructureDefinition/operation-not-supported'): The Implementation Guide contains no examples for this extension (1 uses)
04. This extension is defined in the Expression type, not in this IG
The extension http://hl7.org/fhir/StructureDefinition/elementdefinition-maxValueSet|5.3.0 is deprecated with the note: 'Use additionalBinding extension or element instead' (1 uses)
05. Group profile - this code system is used by the Group resource
Reference to draft CodeSystem http://hl7.org/fhir/group-type|4.0.1 (4 uses)
06. Submission Status Value Set intentionally constrains the FHIR R4 event-status code system for the Bulk Submit submissionStatus parameter. The draft status is inherited from the base FHIR terminology.
Reference to draft CodeSystem http://hl7.org/fhir/event-status|4.0.1 (3 uses)
07. CapabilityStatement.format uses the FHIR R4 MIME type binding; application/fhir+json is the required JSON representation.
Reference to experimental CodeSystem urn:ietf:bcp:13|0.0.2 (0 uses)
08. We have not implemented the Requirements resource nor marked these as conformance clauses in this version, but will consider this as a future enhancement.
%The html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause% (7 uses)
%The html source contains the word 'SHOULD' but it is not in a text phrase marked as a conformance clause% (4 uses)
09. Created UTG tracker to create code system in UTG: UP-759 - "Create an Include Associated Data Code System" based on discussion with TMSG (11/13/2025 minutes: https://confluence.hl7.org/spaces/TSMG/pages/403868663/2025-11-13+TSMG+Agenda+and+Minutes). To preserve the expansion and links in the ValueSet definition, this version will use the current code system defined in this IG and will update to the THO code system URL when it is published. Since the current operation parameter that uses these codes is of type `code` and documented as experimental, this is not considered a breaking change and does not need community input. An STU note was added to alert implementers that that the code system will be migrating to THO.
Most code systems defined in HL7 IGs will need to move to THO later during the process. Consider giving this code system a THO URL now (See https://confluence.hl7.org/display/TSMG/Terminology+Play+Book, and/or talk to TSMG) (1 uses)
hl7.fhir.uv.bulkdata
hl7.terminology.r4
