Profile Comparison between http://hl7.org/fhir/us/core/StructureDefinition/us-core-servicerequest vs http://hl7.org/fhir/us/uds-plus/StructureDefinition/uds-plus-servicerequest

Left:US Core ServiceRequest Profile (http://hl7.org/fhir/us/core/StructureDefinition/us-core-servicerequest)
Right:De-Identified UDS Plus ServiceRequest (http://hl7.org/fhir/us/uds-plus/StructureDefinition/uds-plus-servicerequest)

Messages

ErrorStructureDefinition.urlValues for url differ: 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-servicerequest' vs 'http://hl7.org/fhir/us/uds-plus/StructureDefinition/uds-plus-servicerequest'
ErrorStructureDefinition.versionValues for version differ: '9.0.0-ballot' vs '0.1.0'
InformationStructureDefinition.nameValues for name differ: 'USCoreServiceRequestProfile' vs 'UDSPlusServiceRequest'
InformationStructureDefinition.titleValues for title differ: 'US Core ServiceRequest Profile' vs 'De-Identified UDS Plus ServiceRequest'
InformationStructureDefinition.dateValues for date differ: '2025-04-28' vs '2026-03-16T10:49:09+00:00'
InformationStructureDefinition.publisherValues for publisher differ: 'HL7 International / Cross-Group Projects' vs 'HL7 International / Cross Group Projects'
InformationStructureDefinition.shortValues for short differ: 'A request for a service to be performed' vs 'De-Identified UDS Plus ServiceRequest'
InformationStructureDefinition.definitionValues for definition differ: 'A record of a request for service such as diagnostic investigations, treatments, or operations to be performed.' vs 'The UDS+ profile is based on the ServiceRequest resource and establishes the core elements, extensions, vocabularies and value sets for representing ServiceRequests for UDS+ program.'
InformationStructureDefinition.shortValues for short differ: 'Logical id of this artifact' vs 'The de-identified ServiceRequest identifier created by the health center to send data to UDS+ Data Receiver'
InformationStructureDefinition.definitionValues for definition differ: 'The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.' vs 'De-dentified ServiceRequest resource identifier.'
WarningServiceRequest.idElements differ in definition for mustSupport: 'false' vs 'true'
InformationStructureDefinition.shortValues for short differ: 'Text summary of the resource, for human interpretation' vs 'Cannot include any text in the resource as part of the de-identified data.'
InformationServiceRequest.textElement maximum cardinalities differ: '1' vs '0'
InformationStructureDefinition.shortValues for short differ: 'Contained, inline Resources' vs 'Cannot include any contained resources in the resource as part of the de-identified data.'
InformationServiceRequest.containedElement maximum cardinalities differ: '2147483647' vs '0'
WarningServiceRequest.categoryElements differ in definition for mustSupport: 'true' vs 'false'
WarningServiceRequest.doNotPerformElements differ in definition for mustSupport: 'false' vs 'true'
InformationServiceRequest.doNotPerformElement minimum cardinalities differ: '0' vs '1'
InformationStructureDefinition.shortValues for short differ: '𝗔𝗗𝗗𝗜𝗧𝗜𝗢𝗡𝗔𝗟 𝗨𝗦𝗖𝗗𝗜: Explanation/Justification for procedure or service' vs 'Explanation/Justification for procedure or service'
InformationStructureDefinition.shortValues for short differ: '𝗔𝗗𝗗𝗜𝗧𝗜𝗢𝗡𝗔𝗟 𝗨𝗦𝗖𝗗𝗜: US Core Profile that supports the requested service' vs 'Explanation/Justification for service or service'
WarningServiceRequest.bodySiteElements differ in definition for mustSupport: 'false' vs 'true'

Metadata

NameValueComments
.abstractfalse
    .baseDefinitionhttp://hl7.org/fhir/StructureDefinition/ServiceRequest
      .copyrightUsed by permission of HL7 International, all rights reserved Creative Commons License
      • Removed the item 'Used by permission of HL7 International, all rights reserved Creative Commons License'
      .date2025-04-282026-03-16T10:49:09+00:00
      • Values Differ
      .descriptionThe US Core ServiceRequest Profile inherits from the FHIR [ServiceRequest](https://hl7.org/fhir/R4/servicerequest.html) resource; refer to it for scope and usage definitions. This profile sets minimum expectations for recording, searching, and fetching the ServiceRequest information. It specifies which core elements, extensions, vocabularies, and value sets **SHALL** be present and constrains how the elements are used. Providing the floor for standards development for specific use cases promotes interoperability and adoption.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.
      • Values Differ
      .experimentalfalse
      • Added the item 'false'
      .fhirVersion4.0.1
        .jurisdiction
          ..jurisdiction[0]urn:iso:std:iso:3166#US
            .kindresource
              .nameUSCoreServiceRequestProfileUDSPlusServiceRequest
              • Values Differ
              .publisherHL7 International / Cross-Group ProjectsHL7 International / Cross Group Projects
              • Values Differ
              .purpose
                .statusactive
                  .titleUS Core ServiceRequest ProfileDe-Identified UDS Plus ServiceRequest
                  • Values Differ
                  .typeServiceRequest
                    .urlhttp://hl7.org/fhir/us/core/StructureDefinition/us-core-servicerequesthttp://hl7.org/fhir/us/uds-plus/StructureDefinition/uds-plus-servicerequest
                    • Values Differ
                    .version9.0.0-ballot0.1.0
                    • Values Differ

                    Structure

                    NameL FlagsL Card.L TypeL Description & ConstraintsR FlagsR Card.R TypeR Description & ConstraintsCommentsdoco
                    .. ServiceRequest C0..*ServiceRequestA request for a service to be performed
                    C0..*ServiceRequestDe-Identified UDS Plus ServiceRequest
                      ... id Σ0..1idLogical id of this artifactSΣ0..1idThe de-identified ServiceRequest identifier created by the health center to send data to UDS+ Data Receiver
                      • Elements differ in definition for mustSupport: 'false' vs 'true'
                      ... meta Σ0..1MetaMetadata about the resourceΣ0..1MetaMetadata about the resource
                        ... implicitRules ?!Σ0..1uriA set of rules under which this content was created?!Σ0..1uriA set of rules under which this content was created
                          ... language 0..1codeLanguage of the resource content
                          Binding: ?? (preferred): A human language.
                          Additional BindingsPurpose
                          ??Max Binding
                          0..1codeLanguage of the resource content
                          Binding: ?? (preferred): A human language.
                          Additional BindingsPurpose
                          ??Max Binding
                            ... text 0..1NarrativeText summary of the resource, for human interpretation
                            This profile does not constrain the narrative in regard to content, language, or traceability to data elements
                            0..0Cannot include any text in the resource as part of the de-identified data.
                            This profile does not constrain the narrative in regard to content, language, or traceability to data elements
                            • Element maximum cardinalities differ: '1' vs '0'
                            ... contained 0..*ResourceContained, inline Resources
                            0..0Cannot include any contained resources in the resource as part of the de-identified data.
                            • Element maximum cardinalities differ: '2147483647' vs '0'
                            ... extension 0..*ExtensionAdditional content defined by implementations
                            0..*ExtensionAdditional content defined by implementations
                              ... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
                              ?!0..*ExtensionExtensions that cannot be ignored
                                ... identifier Σ0..*IdentifierIdentifiers assigned to this order
                                Σ0..*IdentifierIdentifiers assigned to this order
                                  ... instantiatesCanonical Σ0..*canonical(ActivityDefinition | PlanDefinition)Instantiates FHIR protocol or definition
                                  Σ0..*canonical(ActivityDefinition | PlanDefinition)Instantiates FHIR protocol or definition
                                    ... instantiatesUri Σ0..*uriInstantiates external protocol or definition
                                    Σ0..*uriInstantiates external protocol or definition
                                      ... basedOn Σ0..*Reference(CarePlan | ServiceRequest | MedicationRequest)What request fulfills
                                      Σ0..*Reference(CarePlan | ServiceRequest | MedicationRequest)What request fulfills
                                        ... replaces Σ0..*Reference(ServiceRequest)What request replaces
                                        Σ0..*Reference(ServiceRequest)What request replaces
                                          ... requisition Σ0..1IdentifierComposite Request IDΣ0..1IdentifierComposite Request ID
                                            ... status ?!SΣ1..1codedraft | active | on-hold | revoked | completed | entered-in-error | unknown
                                            Binding: ?? (required): The status of a service order.
                                            ?!SΣ1..1codedraft | active | on-hold | revoked | completed | entered-in-error | unknown
                                            Binding: ?? (required): The status of a service order.
                                              ... intent ?!SΣ1..1codeproposal | plan | directive | order | original-order | reflex-order | filler-order | instance-order | option
                                              Binding: ?? (required): The kind of service request.
                                              ?!SΣ1..1codeproposal | plan | directive | order | original-order | reflex-order | filler-order | instance-order | option
                                              Binding: ?? (required): The kind of service request.
                                                ... Slices for category SΣ0..*CodeableConceptClassification of service
                                                Slice: Unordered, Open by value:$this
                                                Binding: ?? (example): Classification of the requested service.
                                                Σ0..*CodeableConceptClassification of service
                                                Binding: ?? (example): Classification of the requested service.
                                                • Elements differ in definition for mustSupport: 'true' vs 'false'
                                                ... priority Σ0..1coderoutine | urgent | asap | stat
                                                Binding: ?? (required): Identifies the level of importance to be assigned to actioning the request.
                                                Σ0..1coderoutine | urgent | asap | stat
                                                Binding: ?? (required): Identifies the level of importance to be assigned to actioning the request.
                                                  ... doNotPerform ?!Σ0..1booleanTrue if service/procedure should not be performed?!SΣ1..1booleanTrue if service/procedure should not be performed
                                                  • Elements differ in definition for mustSupport: 'false' vs 'true'
                                                  • Element minimum cardinalities differ: '0' vs '1'
                                                  ... code SΣ1..1CodeableConceptWhat is being requested/ordered
                                                  Binding: ?? (extensible)
                                                  SΣ1..1CodeableConceptWhat is being requested/ordered
                                                  Binding: ?? (extensible): The set of codes indicating the ServiceRequests
                                                    .... id 0..1stringUnique id for inter-element referencing
                                                    • Removed this element
                                                    .... Slices for extension 0..*ExtensionAdditional content defined by implementations
                                                    Slice: Unordered, Open by value:url
                                                    • Removed this element
                                                    .... coding Σ0..*CodingCode defined by a terminology system
                                                    • Removed this element
                                                    .... text Σ0..1string𝗔𝗗𝗗𝗜𝗧𝗜𝗢𝗡𝗔𝗟 𝗨𝗦𝗖𝗗𝗜: The name of the test, procedure, or service to be performed.
                                                    • Removed this element
                                                    ... orderDetail ΣC0..*CodeableConceptAdditional order information
                                                    Binding: ?? (example): Codified order entry details which are based on order context.
                                                    ΣC0..*CodeableConceptAdditional order information
                                                    Binding: ?? (example): Codified order entry details which are based on order context.
                                                      ... quantity[x] Σ0..1Quantity, Ratio, RangeService amountΣ0..1Quantity, Ratio, RangeService amount
                                                        ... subject SΣ1..1Reference(US Core Patient Profile S | Group | US Core Location Profile | US Core Device Profile)Individual or Entity the service is ordered forSΣ1..1Reference(De-Identified UDS Plus Patient)Individual or Entity the service is ordered for
                                                          ... encounter SΣ0..1Reference(US Core Encounter Profile)Encounter in which the request was createdSΣ0..1Reference(De-Identified UDS Plus Encounter)Encounter in which the request was created
                                                            ... occurrence[x] SΣ0..1Period S, dateTime, TimingWhen service should occurSΣ0..1dateTime, Period, TimingWhen service should occur
                                                              ... asNeeded[x] Σ0..1boolean, CodeableConceptPreconditions for service
                                                              Binding: ?? (example): A coded concept identifying the pre-condition that should hold prior to performing a procedure. For example "pain", "on flare-up", etc.
                                                              Σ0..1boolean, CodeableConceptPreconditions for service
                                                              Binding: ?? (example): A coded concept identifying the pre-condition that should hold prior to performing a procedure. For example "pain", "on flare-up", etc.
                                                                ... authoredOn SΣ0..1dateTimeDate request signedSΣ0..1dateTimeDate request signed
                                                                  ... requester SΣ0..1Reference(US Core Practitioner Profile S | US Core Organization Profile | US Core Patient Profile | PractitionerRole | US Core RelatedPerson Profile | US Core Device Profile)Who/what is requesting serviceSΣ0..1Reference(Practitioner | PractitionerRole | Organization | Patient | RelatedPerson | Device)Who/what is requesting service
                                                                    ... performerType Σ0..1CodeableConceptPerformer role
                                                                    Binding: ?? (example): Indicates specific responsibility of an individual within the care team, such as "Primary physician", "Team coordinator", "Caregiver", etc.
                                                                    Σ0..1CodeableConceptPerformer role
                                                                    Binding: ?? (example): Indicates specific responsibility of an individual within the care team, such as "Primary physician", "Team coordinator", "Caregiver", etc.
                                                                      ... performer Σ0..*Reference(Practitioner | PractitionerRole | Organization | CareTeam | HealthcareService | Patient | Device | RelatedPerson)Requested performer
                                                                      Σ0..*Reference(Practitioner | PractitionerRole | Organization | CareTeam | HealthcareService | Patient | Device | RelatedPerson)Requested performer
                                                                        ... locationCode Σ0..*CodeableConceptRequested location
                                                                        Binding: ?? (example): A location type where services are delivered.
                                                                        Σ0..*CodeableConceptRequested location
                                                                        Binding: ?? (example): A location type where services are delivered.
                                                                          ... locationReference Σ0..*Reference(Location)Requested location
                                                                          Σ0..*Reference(Location)Requested location
                                                                            ... reasonCode Σ0..*CodeableConcept𝗔𝗗𝗗𝗜𝗧𝗜𝗢𝗡𝗔𝗟 𝗨𝗦𝗖𝗗𝗜: Explanation/Justification for procedure or service
                                                                            Binding: ?? (extensible)
                                                                            Σ0..*CodeableConceptExplanation/Justification for procedure or service
                                                                            Binding: ?? (example): Diagnosis or problem codes justifying the reason for requesting the service investigation.
                                                                              ... reasonReference Σ0..*Reference(Condition | Observation | DiagnosticReport | DocumentReference)𝗔𝗗𝗗𝗜𝗧𝗜𝗢𝗡𝗔𝗟 𝗨𝗦𝗖𝗗𝗜: US Core Profile that supports the requested service
                                                                              Σ0..*Reference(Condition | Observation | DiagnosticReport | DocumentReference)Explanation/Justification for service or service
                                                                                ... insurance 0..*Reference(Coverage | ClaimResponse)Associated insurance coverage
                                                                                0..*Reference(Coverage | ClaimResponse)Associated insurance coverage
                                                                                  ... supportingInfo 0..*Reference(Resource)Additional clinical information
                                                                                  0..*Reference(Resource)Additional clinical information
                                                                                    ... specimen Σ0..*Reference(Specimen)Procedure Samples
                                                                                    Σ0..*Reference(Specimen)Procedure Samples
                                                                                      ... bodySite Σ0..*CodeableConceptLocation on Body
                                                                                      Binding: ?? (example): Codes describing anatomical locations. May include laterality.
                                                                                      SΣ0..*CodeableConceptLocation on Body
                                                                                      Binding: ?? (example): Codes describing anatomical locations. May include laterality.
                                                                                      • Elements differ in definition for mustSupport: 'false' vs 'true'
                                                                                      ... note 0..*AnnotationComments
                                                                                      0..*AnnotationComments
                                                                                        ... patientInstruction Σ0..1stringPatient or consumer-oriented instructionsΣ0..1stringPatient or consumer-oriented instructions
                                                                                          ... relevantHistory 0..*Reference(Provenance)Request provenance
                                                                                          0..*Reference(Provenance)Request provenance

                                                                                            doco Documentation for this format