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

Left:US Core ServiceRequest Profile (http://hl7.org/fhir/us/core/StructureDefinition/us-core-servicerequest)
Right:US Core PMO ServiceRequest Profile (http://hl7.org/fhir/us/core/StructureDefinition/us-core-pmo-servicerequest)

Messages

ErrorStructureDefinition.urlValues for url differ: 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-servicerequest' vs 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-pmo-servicerequest'
ErrorStructureDefinition.versionValues for version differ: '8.0.0' vs '0.1.0'
InformationStructureDefinition.nameValues for name differ: 'USCoreServiceRequestProfile' vs 'USCorePMOServiceRequestProfile'
InformationStructureDefinition.titleValues for title differ: 'US Core ServiceRequest Profile' vs 'US Core PMO ServiceRequest Profile'
InformationStructureDefinition.statusValues for status differ: 'active' vs 'draft'
InformationStructureDefinition.dateValues for date differ: '2025-04-28' vs '2025-08-26'
InformationStructureDefinition.publisherValues for publisher differ: 'HL7 International / Cross-Group Projects' vs 'HL7 International / Payer/Provider Information Exchange Work Group'
InformationServiceRequest.languageExample/preferred bindings differ at ServiceRequest.language using binding from USCoreServiceRequestProfile
InformationStructureDefinition.shortValues for short differ: 'proposal | plan | directive | order | original-order | reflex-order | filler-order | instance-order | option' vs 'Note: To allow for the resource life cycle, no constraint on intent, use 'directive' in PMO document'
ErrorServiceRequest.codeUnable to resolve right value set http://hl7.org/fhir/us/core/ValueSet/us-core-pmo-procedure-code at ServiceRequest.code
InformationStructureDefinition.shortValues for short differ: '𝗔𝗗𝗗𝗜𝗧𝗜𝗢𝗡𝗔𝗟 𝗨𝗦𝗖𝗗𝗜: The name of the test, procedure, or service to be performed.' vs 'Plain text representation of the PMO procedure or service.'
WarningServiceRequest.code.textElements differ in definition for mustSupport: 'false' vs 'true'
WarningServiceRequest.orderDetailElements differ in definition for mustSupport: 'false' vs 'true'
InformationStructureDefinition.shortValues for short differ: 'Individual or Entity the service is ordered for' vs 'limited to Patient'
InformationStructureDefinition.shortValues for short differ: 'Encounter in which the request was created' vs '**NOT USED WHEN PART OF A PMO DOCUMENT**'
InformationStructureDefinition.shortValues for short differ: 'When service should occur' vs 'Often just a start date'
InformationStructureDefinition.shortValues for short differ: 'Date request signed' vs 'Date Order signed vs date of PMO document - same if part of PMO document'
InformationStructureDefinition.shortValues for short differ: 'Who/what is requesting service' vs 'Authored only by Practitioner'
InformationStructureDefinition.shortValues for short differ: '𝗔𝗗𝗗𝗜𝗧𝗜𝗢𝗡𝗔𝗟 𝗨𝗦𝗖𝗗𝗜: Explanation/Justification for procedure or service' vs 'Explanation/Justification for procedure or service'
WarningServiceRequest.reasonCodeElements differ in definition for mustSupport: 'false' vs 'true'
InformationStructureDefinition.shortValues for short differ: '𝗔𝗗𝗗𝗜𝗧𝗜𝗢𝗡𝗔𝗟 𝗨𝗦𝗖𝗗𝗜: US Core Profile that supports the requested service' vs 'US Core ADI DocumentReference Profile or other US Core profiles that support the requested PMO service.'
WarningServiceRequest.reasonReferenceElements differ in definition for mustSupport: 'false' vs 'true'
ErrorServiceRequest.reasonReferenceType Mismatch: Reference([CanonicalType[http://hl7.org/fhir/StructureDefinition/Condition], CanonicalType[http://hl7.org/fhir/StructureDefinition/Observation], CanonicalType[http://hl7.org/fhir/StructureDefinition/DiagnosticReport], CanonicalType[http://hl7.org/fhir/StructureDefinition/DocumentReference]]) vs Reference([CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-adi-documentreference], CanonicalType[http://hl7.org/fhir/StructureDefinition/us-core-condition], CanonicalType[http://hl7.org/fhir/StructureDefinition/us-core-observation], CanonicalType[http://hl7.org/fhir/StructureDefinition/us-core-diagnosticreport]])

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-282025-08-26
      • 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 US Core PMO 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 represents an order based on a PMO document and references the [US Core ADI DocumentReference Profile](StructureDefinition-us-core-adi-documentreference.html) to communicate the contents of the PMO document, such as POLST, MOLST, or other state-specific forms. PMO documents follow the patient across care settings and are typically stored as scanned images in EMRs/EHRs. Together, these two profiles satisfy the USCDI's PMO Order Data Element's intent to represent orders based on an individual's PMO. The US Core PMO ServiceRequest Profile establishes minimum expectations for recording, searching, and fetching PMO-related ServiceRequest information, specifying core elements, extensions, vocabularies, and value sets that SHALL be present to promote interoperability.
      • Values Differ
      .experimental
        .fhirVersion4.0.1
          .jurisdiction
            ..jurisdiction[0]urn:iso:std:iso:3166#US
              .kindresource
                .nameUSCoreServiceRequestProfileUSCorePMOServiceRequestProfile
                • Values Differ
                .publisherHL7 International / Cross-Group ProjectsHL7 International / Payer/Provider Information Exchange Work Group
                • Values Differ
                .purpose
                  .statusactivedraft
                  • Values Differ
                  .titleUS Core ServiceRequest ProfileUS Core PMO ServiceRequest Profile
                  • Values Differ
                  .typeServiceRequest
                    .urlhttp://hl7.org/fhir/us/core/StructureDefinition/us-core-servicerequesthttp://hl7.org/fhir/us/core/StructureDefinition/us-core-pmo-servicerequest
                    • Values Differ
                    .version8.0.00.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..*ServiceRequestA request for a service to be performed
                      ... id Σ0..1idLogical id of this artifactΣ0..1idLogical id of this artifact
                        ... 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
                            • Example/preferred bindings differ at ServiceRequest.language using binding from USCoreServiceRequestProfile
                            ... 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..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
                              ... contained 0..*ResourceContained, inline Resources
                              0..*ResourceContained, inline Resources
                                ... 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..1codeNote: To allow for the resource life cycle, no constraint on intent, use "directive" in PMO document
                                                  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.
                                                    SΣ0..*CodeableConceptClassification of service
                                                    Slice: Unordered, Open by value:$this
                                                    Binding: ?? (example): Classification of the requested service.
                                                      ... 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?!Σ0..1booleanTrue if service/procedure should not be performed
                                                          ... code SΣ1..1CodeableConceptWhat is being requested/ordered
                                                          Binding: ?? (extensible)
                                                          SΣ1..1CodeableConceptWhat is being requested/ordered
                                                          Binding: ?? (extensible): Portable Medical Order panel answers - mostly free-text
                                                          Additional BindingsPurposeDocumentation
                                                          ??Extensible
                                                          SeviceRequest.category = Cardiopulmonary resuscitation orders
                                                          ??Extensible
                                                          SeviceRequest.category = Initial portable medical treatment orders
                                                          ??Extensible
                                                          SeviceRequest.category = Additional portable medical orders or instructions
                                                          • Unable to resolve right value set http://hl7.org/fhir/us/core/ValueSet/us-core-pmo-procedure-code at ServiceRequest.code
                                                          .... id 0..1stringUnique id for inter-element referencing0..1stringUnique id for inter-element referencing
                                                            .... Slices for extension 0..*ExtensionAdditional content defined by implementations
                                                            Slice: Unordered, Open by value:url
                                                            0..*ExtensionAdditional content defined by implementations
                                                            Slice: Unordered, Open by value:url
                                                              .... coding Σ0..*CodingCode defined by a terminology system
                                                              Σ0..*CodingCode defined by a terminology system
                                                                .... text Σ0..1string𝗔𝗗𝗗𝗜𝗧𝗜𝗢𝗡𝗔𝗟 𝗨𝗦𝗖𝗗𝗜: The name of the test, procedure, or service to be performed.SΣ0..1stringPlain text representation of the PMO procedure or service.
                                                                • Elements differ in definition for mustSupport: 'false' vs 'true'
                                                                ... orderDetail ΣC0..*CodeableConceptAdditional order information
                                                                Binding: ?? (example): Codified order entry details which are based on order context.
                                                                SΣC0..*CodeableConceptAdditional order information
                                                                Binding: ?? (example): Codified order entry details which are based on order context.
                                                                • Elements differ in definition for mustSupport: 'false' vs 'true'
                                                                .... id 0..1stringUnique id for inter-element referencing
                                                                • Added this element
                                                                .... Slices for extension 0..*ExtensionAdditional content defined by implementations
                                                                Slice: Unordered, Open by value:url
                                                                • Added this element
                                                                .... coding Σ0..*CodingCode defined by a terminology system
                                                                • Added this element
                                                                .... text SΣ0..1stringPlain text representation to capture additional PMO order details.
                                                                • Added this element
                                                                ... 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 | Device)Individual or Entity the service is ordered forSΣ1..1Reference(US Core Patient Profile)limited to Patient
                                                                    ... encounter SΣ0..1Reference(US Core Encounter Profile)Encounter in which the request was createdSΣ0..1Reference(US Core Encounter Profile)**NOT USED WHEN PART OF A PMO DOCUMENT**
                                                                      ... occurrence[x] SΣ0..1Period S, dateTime, TimingWhen service should occurSΣ0..1Period S, dateTime, TimingOften just a start date
                                                                        ... 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 Order signed vs date of PMO document - same if part of PMO document
                                                                            ... requester SΣ0..1Reference(US Core Practitioner Profile S | US Core Organization Profile | US Core Patient Profile | PractitionerRole | US Core RelatedPerson Profile | Device)Who/what is requesting serviceSΣ0..1Reference(US Core Practitioner Profile S | US Core Organization Profile | PractitionerRole)Authored only by Practitioner
                                                                              ... 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)
                                                                                      SΣ0..*CodeableConceptExplanation/Justification for procedure or service
                                                                                      Binding: ?? (extensible)
                                                                                      • Elements differ in definition for mustSupport: 'false' vs 'true'
                                                                                      ... reasonReference Σ0..*Reference(Condition | Observation | DiagnosticReport | DocumentReference)𝗔𝗗𝗗𝗜𝗧𝗜𝗢𝗡𝗔𝗟 𝗨𝗦𝗖𝗗𝗜: US Core Profile that supports the requested service
                                                                                      SΣ0..*Reference(US Core ADI DocumentReference Profile S | us-core-condition | us-core-observation | us-core-diagnosticreport)US Core ADI DocumentReference Profile or other US Core profiles that support the requested PMO service.
                                                                                      • Elements differ in definition for mustSupport: 'false' vs 'true'
                                                                                      • Type Mismatch: Reference([CanonicalType[http://hl7.org/fhir/StructureDefinition/Condition], CanonicalType[http://hl7.org/fhir/StructureDefinition/Observation], CanonicalType[http://hl7.org/fhir/StructureDefinition/DiagnosticReport], CanonicalType[http://hl7.org/fhir/StructureDefinition/DocumentReference]]) vs Reference([CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-adi-documentreference], CanonicalType[http://hl7.org/fhir/StructureDefinition/us-core-condition], CanonicalType[http://hl7.org/fhir/StructureDefinition/us-core-observation], CanonicalType[http://hl7.org/fhir/StructureDefinition/us-core-diagnosticreport]])
                                                                                      ... 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.
                                                                                            Σ0..*CodeableConceptLocation on Body
                                                                                            Binding: ?? (example): Codes describing anatomical locations. May include laterality.
                                                                                              ... 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