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

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

Messages

ErrorStructureDefinition.urlValues for url differ: 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-pmo-servicerequest' vs 'http://hl7.org/fhir/us/dapl/StructureDefinition/dapl-servicerequest'
ErrorStructureDefinition.versionValues for version differ: '9.0.0-ballot' vs '0.1.0'
InformationStructureDefinition.nameValues for name differ: 'USCorePMOServiceRequestProfile' vs 'DAPLServiceRequest'
InformationStructureDefinition.titleValues for title differ: 'US Core PMO ServiceRequest Profile' vs 'DAPL ServiceRequest'
InformationStructureDefinition.dateValues for date differ: '2025-08-26' vs '2026-03-26T14:18:44+00:00'
InformationStructureDefinition.shortValues for short differ: 'A request for a service to be performed' vs 'DAPL 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 DAPL profile establishes the core elements, extensions, vocabularies and value sets for representing deidentified and anonymized ServiceRequests.'
InformationStructureDefinition.shortValues for short differ: 'Logical id of this artifact' vs 'The ServiceRequest identifier created by the DARTS services potentially linked back to the original ServiceRequest as needed.'
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 'DARTS 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 or anonymized 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 or anonymized data.'
InformationServiceRequest.containedElement maximum cardinalities differ: '2147483647' vs '0'
InformationStructureDefinition.commentValues for comment differ: 'To allow for the resource life cycle, no constraint on intent for use when documenting derived medical orders. Use 'directive' when part of a FHIR-based PMO document.' vs 'This element is labeled as a modifier because the intent alters when and how the resource is actually applicable.'
WarningServiceRequest.categoryElements differ in definition for mustSupport: 'true' vs 'false'
InformationServiceRequest.categoryElement minimum cardinalities differ: '1' vs '0'
WarningServiceRequest.doNotPerformElements differ in definition for mustSupport: 'false' vs 'true'
InformationServiceRequest.doNotPerformElement minimum cardinalities differ: '0' vs '1'
InformationStructureDefinition.commentValues for comment differ: 'The `ServiceRequest.code` is bound to [Portable Medical Orders - Detailed Categories and Interventions](https://vsac.nlm.nih.gov/valueset/2.16.840.1.113762.1.4.1267.35/expansion), which is comprised of code sets for each [Portable Medical Order Categories](https://vsac.nlm.nih.gov/valueset/2.16.840.1.113762.1.4.1267.34/Expansion) found in `ServiceRequest.category:us-core-pmo-category`. For proper context, these codes **SHOULD** be aligned with the appropriate Category as follows. - When there is no appropriate code to capture the order, plain text can be used here and in the optional `ServiceRequest.orderDetail` element.' vs 'Many laboratory and radiology procedure codes embed the specimen/organ system in the test order name, for example, serum or serum/plasma glucose, or a chest x-ray. The specimen might not be recorded separately from the test code.'
InformationStructureDefinition.shortValues for short differ: 'Reference to the PMO document' vs 'Explanation/Justification for service or service'
WarningServiceRequest.reasonReferenceElements differ in definition for mustSupport: 'true' vs 'false'
ErrorServiceRequest.reasonReferenceType Mismatch: Reference([CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-adi-documentreference], CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-documentreference], CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-condition-problems-health-concerns], CanonicalType[http://hl7.org/fhir/StructureDefinition/Observation], CanonicalType[http://hl7.org/fhir/StructureDefinition/DiagnosticReport]]) vs Reference([CanonicalType[http://hl7.org/fhir/StructureDefinition/Condition|4.0.1], CanonicalType[http://hl7.org/fhir/StructureDefinition/Observation|4.0.1], CanonicalType[http://hl7.org/fhir/StructureDefinition/DiagnosticReport|4.0.1], CanonicalType[http://hl7.org/fhir/StructureDefinition/DocumentReference|4.0.1]])
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-08-262026-03-26T14:18:44+00:00
      • Values Differ
      .descriptionThe 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. The DAPL profile establishes the core elements, extensions, vocabularies and value sets for representing deidentified and anonymized ServiceRequest.
      • Values Differ
      .experimentalfalse
      • Added the item 'false'
      .fhirVersion4.0.1
        .jurisdiction
          ..jurisdiction[0]urn:iso:std:iso:3166#US
            .kindresource
              .nameUSCorePMOServiceRequestProfileDAPLServiceRequest
              • Values Differ
              .publisherHL7 International / Cross-Group Projects
                .purpose
                  .statusactive
                    .titleUS Core PMO ServiceRequest ProfileDAPL ServiceRequest
                    • Values Differ
                    .typeServiceRequest
                      .urlhttp://hl7.org/fhir/us/core/StructureDefinition/us-core-pmo-servicerequesthttp://hl7.org/fhir/us/dapl/StructureDefinition/dapl-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..*ServiceRequestDAPL ServiceRequest
                        ... id Σ0..1idLogical id of this artifactSΣ0..1idThe ServiceRequest identifier created by the DARTS services potentially linked back to the original ServiceRequest as needed.
                        • 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 or anonymized 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 or anonymized 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Σ1..*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'
                                                  • Element minimum cardinalities differ: '1' vs '0'
                                                  ... 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
                                                      ... 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)Individual or Entity the service is ordered forSΣ1..1Reference(DAPL Deidentified 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(DAPL Deidentified 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 | PractitionerRole)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..*CodeableConceptExplanation/Justification for procedure or service
                                                                              Binding: ?? (example): Diagnosis or problem codes justifying the reason for requesting the service investigation.
                                                                              Σ0..*CodeableConceptExplanation/Justification for procedure or service
                                                                              Binding: ?? (example): Diagnosis or problem codes justifying the reason for requesting the service investigation.
                                                                                ... reasonReference SΣ0..*Reference(US Core ADI DocumentReference Profile S | US Core DocumentReference Profile | US Core Condition Problems and Health Concerns Profile | Observation | DiagnosticReport)Reference to the PMO document
                                                                                Σ0..*Reference(Condition | Observation | DiagnosticReport | DocumentReference)Explanation/Justification for service or service
                                                                                • Elements differ in definition for mustSupport: 'true' vs 'false'
                                                                                • Type Mismatch: Reference([CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-adi-documentreference], CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-documentreference], CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-condition-problems-health-concerns], CanonicalType[http://hl7.org/fhir/StructureDefinition/Observation], CanonicalType[http://hl7.org/fhir/StructureDefinition/DiagnosticReport]]) vs Reference([CanonicalType[http://hl7.org/fhir/StructureDefinition/Condition|4.0.1], CanonicalType[http://hl7.org/fhir/StructureDefinition/Observation|4.0.1], CanonicalType[http://hl7.org/fhir/StructureDefinition/DiagnosticReport|4.0.1], CanonicalType[http://hl7.org/fhir/StructureDefinition/DocumentReference|4.0.1]])
                                                                                ... 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