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

Left:US Core ServiceRequest Profile (http://hl7.org/fhir/us/core/StructureDefinition/us-core-servicerequest)
Right:PCT GFE ServiceRequest (http://hl7.org/fhir/us/davinci-pct/StructureDefinition/davinci-pct-servicerequest)

Messages

ErrorStructureDefinition.urlValues for url differ: 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-servicerequest' vs 'http://hl7.org/fhir/us/davinci-pct/StructureDefinition/davinci-pct-servicerequest'
ErrorStructureDefinition.versionValues for version differ: '7.0.0' vs '2.0.0-ballot'
InformationStructureDefinition.nameValues for name differ: 'USCoreServiceRequestProfile' vs 'PCTServiceRequest'
InformationStructureDefinition.titleValues for title differ: 'US Core ServiceRequest Profile' vs 'PCT GFE ServiceRequest'
InformationStructureDefinition.dateValues for date differ: '2023-10-17' vs '2024-11-20T18:01:40+00:00'
InformationStructureDefinition.publisherValues for publisher differ: 'HL7 International / Cross-Group Projects' vs 'HL7 International / Financial Management'
InformationStructureDefinition.commentValues for comment differ: 'The status is generally fully in the control of the requester - they determine whether the order is draft or active and, after it has been activated, competed, cancelled or suspended. States relating to the activities of the performer are reflected on either the corresponding event (see [Event Pattern](event.html) for general discussion) or using the [Task](task.html) resource.' vs 'The status is generally fully in the control of the requester - they determine whether the order is draft or active and, after it has been activated, competed, cancelled or suspended. States relating to the activities of the performer are reflected on either the corresponding event (see [Event Pattern](http://hl7.org/fhir/R4/event.html) for general discussion) or using the [Task](http://hl7.org/fhir/R4/task.html) resource.'
WarningServiceRequest.statusElements differ in definition for mustSupport: 'true' vs 'false'
WarningServiceRequest.intentElements differ in definition for mustSupport: 'true' vs 'false'
WarningServiceRequest.categoryElements differ in definition for mustSupport: 'true' vs 'false'
InformationServiceRequest.doNotPerformElement maximum cardinalities differ: '1' vs '0'
WarningServiceRequest.quantity[x]Elements differ in definition for mustSupport: 'false' vs 'true'
WarningServiceRequest.subjectElements differ in definition for mustSupport: 'true' vs 'false'
WarningServiceRequest.encounterElements differ in definition for mustSupport: 'true' vs 'false'
WarningServiceRequest.occurrence[x]Elements differ in definition for mustSupport: 'true' vs 'false'
WarningServiceRequest.authoredOnElements differ in definition for mustSupport: 'true' vs 'false'
WarningServiceRequest.requesterElements differ in definition for mustSupport: 'true' vs 'false'
InformationStructureDefinition.shortValues for short differ: '𝗔𝗗𝗗𝗜𝗧𝗜𝗢𝗡𝗔𝗟 𝗨𝗦𝗖𝗗𝗜: Explanation/Justification for procedure or service' vs 'Explanation/Justification for procedure or service'
InformationStructureDefinition.commentValues for comment differ: 'This element represents why the referral is being made and may be used to decide how the service will be performed, or even if it will be performed at all. Use `CodeableConcept.text` element if the data is free (uncoded) text as shown in the [CT Scan example](servicerequest-example-di.html).' vs 'This element represents why the referral is being made and may be used to decide how the service will be performed, or even if it will be performed at all. Use `CodeableConcept.text` element if the data is free (uncoded) text as shown in the [CT Scan example](http://hl7.org/fhir/R4/servicerequest-example-di.html).'
InformationStructureDefinition.shortValues for short differ: '𝗔𝗗𝗗𝗜𝗧𝗜𝗢𝗡𝗔𝗟 𝗨𝗦𝗖𝗗𝗜: US Core Profile that supports the requested service' vs 'Explanation/Justification for service or service'
InformationStructureDefinition.commentValues for comment differ: 'This element represents why the referral is being made and may be used to decide how the service will be performed, or even if it will be performed at all. To be as specific as possible, a reference to *Observation* or *Condition* should be used if available. Otherwise when referencing *DiagnosticReport* it should contain a finding in `DiagnosticReport.conclusion` and/or `DiagnosticReport.conclusionCode`. When using a reference to *DocumentReference*, the target document should contain clear findings language providing the relevant reason for this service request. Use the CodeableConcept text element in `ServiceRequest.reasonCode` if the data is free (uncoded) text as shown in the [CT Scan example](servicerequest-example-di.html).' vs 'This element represents why the referral is being made and may be used to decide how the service will be performed, or even if it will be performed at all. To be as specific as possible, a reference to *Observation* or *Condition* should be used if available. Otherwise when referencing *DiagnosticReport* it should contain a finding in `DiagnosticReport.conclusion` and/or `DiagnosticReport.conclusionCode`. When using a reference to *DocumentReference*, the target document should contain clear findings language providing the relevant reason for this service request. Use the CodeableConcept text element in `ServiceRequest.reasonCode` if the data is free (uncoded) text as shown in the [CT Scan example](http://hl7.org/fhir/R4/servicerequest-example-di.html).'
InformationStructureDefinition.commentValues for comment differ: 'Many diagnostic procedures need a specimen, but the request itself is not actually about the specimen. This element is for when the diagnostic is requested on already existing specimens and the request points to the specimen it applies to. Conversely, if the request is entered first with an unknown specimen, then the [Specimen](specimen.html) resource points to the ServiceRequest.' vs 'Many diagnostic procedures need a specimen, but the request itself is not actually about the specimen. This element is for when the diagnostic is requested on already existing specimens and the request points to the specimen it applies to. Conversely, if the request is entered first with an unknown specimen, then the [Specimen](http://hl7.org/fhir/R4/specimen.html) resource points to the ServiceRequest.'

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'
      .date2023-10-172024-11-20T18:01:40+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 PCT ServiceRequest including details about a service for which a GFE is being requested.
      • Values Differ
      .experimental
        .fhirVersion4.0.1
          .jurisdiction
            ..jurisdiction[0]urn:iso:std:iso:3166#US
              .kindresource
                .nameUSCoreServiceRequestProfilePCTServiceRequest
                • Values Differ
                .publisherHL7 International / Cross-Group ProjectsHL7 International / Financial Management
                • Values Differ
                .purpose
                  .statusactive
                    .titleUS Core ServiceRequest ProfilePCT GFE ServiceRequest
                    • Values Differ
                    .typeServiceRequest
                      .urlhttp://hl7.org/fhir/us/core/StructureDefinition/us-core-servicerequesthttp://hl7.org/fhir/us/davinci-pct/StructureDefinition/davinci-pct-servicerequest
                      • Values Differ
                      .version7.0.02.0.0-ballot
                      • 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
                      prr-1: orderDetail SHALL only be present if code is present
                      C0..*ServiceRequestA request for a service to be performed
                      prr-1: orderDetail SHALL only be present if code is present
                        ... 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
                                ... text 0..1NarrativeText summary of the resource, for human interpretation0..1NarrativeText summary of the resource, for human interpretation
                                  ... 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.

                                                    ?!Σ1..1codedraft | active | on-hold | revoked | completed | entered-in-error | unknown
                                                    Binding: ?? (required): The status of a service order.


                                                    Required Pattern: active
                                                    • Elements differ in definition for mustSupport: 'true' vs 'false'
                                                    ... intent ?!SΣ1..1codeproposal | plan | directive | order | original-order | reflex-order | filler-order | instance-order | option
                                                    Binding: ?? (required): The kind of service request.

                                                    ?!Σ1..1codeproposal | plan | directive | order | original-order | reflex-order | filler-order | instance-order | option
                                                    Binding: ?? (required): The kind of service request.


                                                    Required Pattern: proposal
                                                    • Elements differ in definition for mustSupport: 'true' vs 'false'
                                                    ... Slices for category SΣ0..*CodeableConceptClassification of service
                                                    Slice: Unordered, Open by pattern:$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?!Σ0..0
                                                      • Element maximum cardinalities differ: '1' vs '0'
                                                      ... code SΣ1..1CodeableConceptWhat is being requested/ordered
                                                      Binding: ?? (extensible)
                                                      SΣ1..1CodeableConceptWhat is being requested/ordered
                                                      Binding: ?? (extensible)
                                                        ... 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 amountSΣ0..1Quantity, Ratio, RangeService amount
                                                          • Elements differ in definition for mustSupport: 'false' vs 'true'
                                                          ... subject SΣ1..1Reference(US Core Patient Profile S | Group | US Core Location Profile | Device)Individual or Entity the service is ordered forΣ1..1Reference(HRex Patient Demographics)Individual or Entity the service is ordered for
                                                          • Elements differ in definition for mustSupport: 'true' vs 'false'
                                                          ... encounter SΣ0..1Reference(US Core Encounter Profile)Encounter in which the request was createdΣ0..1Reference(Encounter)Encounter in which the request was created
                                                          • Elements differ in definition for mustSupport: 'true' vs 'false'
                                                          ... occurrence[x] SΣ0..1Period S, dateTime, TimingWhen service should occurΣ0..1dateTime, Period, TimingWhen service should occur
                                                          • Elements differ in definition for mustSupport: 'true' vs 'false'
                                                          ... 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 signedΣ0..1dateTimeDate request signed
                                                            • Elements differ in definition for mustSupport: 'true' vs 'false'
                                                            ... 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 serviceΣ0..1Reference(Practitioner | PractitionerRole | Organization | Patient | RelatedPerson | Device)Who/what is requesting service
                                                            • Elements differ in definition for mustSupport: 'true' vs 'false'
                                                            ... 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.


                                                                              Σ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