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

Left:US Core ServiceRequest Profile (http://hl7.org/fhir/us/core/StructureDefinition/us-core-servicerequest)
Right:Dental Service Request (http://hl7.org/fhir/us/dental-data-exchange/dental-servicerequest)

Messages

ErrorStructureDefinition.urlValues for url differ: 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-servicerequest' vs 'http://hl7.org/fhir/us/dental-data-exchange/dental-servicerequest'
ErrorStructureDefinition.versionValues for version differ: '7.0.0' vs '2.0.0-ballot'
InformationStructureDefinition.nameValues for name differ: 'USCoreServiceRequestProfile' vs 'DentalServiceRequest'
InformationStructureDefinition.titleValues for title differ: 'US Core ServiceRequest Profile' vs 'Dental Service Request'
InformationStructureDefinition.dateValues for date differ: '2023-10-17' vs '2024-09-11T14:08:38+00:00'
InformationStructureDefinition.publisherValues for publisher differ: 'HL7 International / Cross-Group Projects' vs 'Payer/Provider Information Exchange Work Group'
WarningServiceRequest.identifierElements differ in definition for mustSupport: 'false' vs 'true'
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'
WarningServiceRequest.priorityElements differ in definition for mustSupport: 'false' vs 'true'
InformationServiceRequest.codeElement minimum cardinalities differ: '1' vs '0'
WarningServiceRequest.subjectElements differ in definition for mustSupport: 'true' vs 'false'
WarningServiceRequest.encounterElements 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'
WarningServiceRequest.reasonCodeElements differ in definition for mustSupport: 'false' vs 'true'
InformationStructureDefinition.shortValues for short differ: '𝗔𝗗𝗗𝗜𝗧𝗜𝗢𝗡𝗔𝗟 𝗨𝗦𝗖𝗗𝗜: US Core Profile that supports the requested service' vs 'Explanation/Justification for service or service'
WarningServiceRequest.insuranceElements differ in definition for mustSupport: 'false' vs 'true'
WarningServiceRequest.supportingInfoElements 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'
      .date2023-10-172024-09-11T14:08:38+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.This profile contains information regarding the dental referral request including an identifier and a reference to the reason for the referral, if possible. It also includes basic information such as the patient, referring provider, and encounter information that resulted in the referral.
      • Values Differ
      .experimental
        .fhirVersion4.0.1
          .jurisdiction
            ..jurisdiction[0]urn:iso:std:iso:3166#US
              .kindresource
                .nameUSCoreServiceRequestProfileDentalServiceRequest
                • Values Differ
                .publisherHL7 International / Cross-Group ProjectsPayer/Provider Information Exchange Work Group
                • Values Differ
                .purpose
                  .statusactive
                    .titleUS Core ServiceRequest ProfileDental Service Request
                    • Values Differ
                    .typeServiceRequest
                      .urlhttp://hl7.org/fhir/us/core/StructureDefinition/us-core-servicerequesthttp://hl7.org/fhir/us/dental-data-exchange/dental-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
                                        SΣ0..*IdentifierIdentifiers assigned to this order
                                        • Elements differ in definition for mustSupport: 'false' vs 'true'
                                        ... 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.

                                                  • 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.

                                                  • 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.

                                                  SΣ0..1coderoutine | urgent | asap | stat
                                                  Binding: ?? (required): Identifies the level of importance to be assigned to actioning the request.

                                                  • Elements differ in definition for mustSupport: 'false' vs 'true'
                                                  ... 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Σ0..1CodeableConceptWhat is being requested/ordered
                                                    Binding: ?? (example): Codes for tests or services that can be carried out by a designated individual, organization or healthcare service. For laboratory, LOINC is (preferred)[http://build.fhir.org/terminologies.html#preferred] and a valueset using LOINC Order codes is available here.

                                                    • Element minimum cardinalities differ: '1' vs '0'
                                                    ... 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(4.0.0) S | Group | US Core Location Profile(4.0.0) | Device)Individual or Entity the service is ordered forΣ1..1Reference(US Core Patient Profile(4.0.0))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(4.0.0))Encounter in which the request was createdΣ0..1Reference(US Core Encounter Profile(4.0.0))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 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 signedΣ0..1dateTimeDate request signed
                                                            • Elements differ in definition for mustSupport: 'true' vs 'false'
                                                            ... requester SΣ0..1Reference(US Core Practitioner Profile(4.0.0) S | US Core Organization Profile(4.0.0) | US Core Patient Profile(4.0.0) | 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)
                                                                    SΣ0..*CodeableConceptExplanation/Justification for procedure or service
                                                                    Binding: ?? (preferred)
                                                                    • Elements differ in definition for mustSupport: 'false' vs 'true'
                                                                    ... 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
                                                                      S0..*Reference(HRex Coverage Profile)Associated insurance coverage
                                                                      • Elements differ in definition for mustSupport: 'false' vs 'true'
                                                                      ... supportingInfo 0..*Reference(Resource)Additional clinical information
                                                                      S0..*Reference(Resource)Additional clinical information
                                                                      • Elements differ in definition for mustSupport: 'false' vs 'true'
                                                                      ... 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