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

Left:US Core Service Request (http://hl7.org/fhir/us/core/StructureDefinition/us-core-servicerequest)
Right:PAS Service Request (http://hl7.org/fhir/us/davinci-pas/StructureDefinition/profile-servicerequest)

Messages

ErrorStructureDefinition.urlValues for url differ: 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-servicerequest' vs 'http://hl7.org/fhir/us/davinci-pas/StructureDefinition/profile-servicerequest'
ErrorStructureDefinition.versionValues for version differ: '4.1.0' vs '1.2.0-ballot'
InformationStructureDefinition.nameValues for name differ: 'USCoreServiceRequest' vs 'PASServiceRequest'
InformationStructureDefinition.titleValues for title differ: 'US Core Service Request' vs 'PAS Service Request'
InformationStructureDefinition.dateValues for date differ: '2018-08-22T00:00:00+00:00' vs '2022-02-17T07:51:22+00:00'
InformationStructureDefinition.publisherValues for publisher differ: 'HL7 International - Cross-Group Projects' vs 'HL7 International - Financial Management Work Group'
WarningServiceRequest.extensionElements differ in short: 'Additional content defined by implementations' vs 'Extension'
WarningServiceRequest.extensionElements differ in definition: 'May be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.' vs 'An Extension'
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.categoryElement minimum cardinalities differ: '1' vs '0'
InformationServiceRequest.codeElement minimum cardinalities differ: '1' vs '0'
WarningServiceRequest.quantity[x]Elements differ in definition for mustSupport: 'false' vs 'true'
WarningServiceRequest.occurrence[x]Elements differ in short: 'When service should occur' vs 'A timing schedule that specifies an event that may occur multiple times'
WarningServiceRequest.occurrence[x]Elements differ in definition: 'The date/time at which the requested service should occur.' vs 'Specifies an event that may occur multiple times. Timing schedules are used to record when things are planned, expected or requested to occur. The most common usage is in dosage instructions for medications. They are also used when planning care of various kinds, and may be used for reporting the schedule to which past regular activities were carried out.'
WarningServiceRequest.authoredOnElements differ in definition for mustSupport: 'true' vs 'false'
WarningServiceRequest.requesterElements differ in definition for mustSupport: 'true' vs 'false'

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'
      .date2018-08-22T00:00:00+00:002022-02-17T07:51:22+00:00
      • Values Differ
      .descriptionDefines constraints and extensions on the ServiceRequest resource for the minimal set of data to query and retrieve orders associated with diagnostic and clinical tests and clinical interventions for a patientPAS constraints on ServiceRequest resource mandating support for elements relevant to the generic services being requested on a prior authorization request
      • Values Differ
      .experimental
        .fhirVersion4.0.1
          .jurisdiction
            ..jurisdiction[0]urn:iso:std:iso:3166#US
              .kindresource
                .nameUSCoreServiceRequestPASServiceRequest
                • Values Differ
                .publisherHL7 International - Cross-Group ProjectsHL7 International - Financial Management Work Group
                • Values Differ
                .purpose
                  .statusactive
                    .titleUS Core Service RequestPAS Service Request
                    • Values Differ
                    .typeServiceRequest
                      .urlhttp://hl7.org/fhir/us/core/StructureDefinition/us-core-servicerequesthttp://hl7.org/fhir/us/davinci-pas/StructureDefinition/profile-servicerequest
                      • Values Differ
                      .version4.1.01.2.0-ballot
                      • Values Differ

                      Structure

                      NameL FlagsL Card.L TypeL Description & ConstraintsR FlagsR Card.L TypeL Description & ConstraintsCommentsdoco
                      .. ServiceRequest I0..*ServiceRequestA request for a service to be performed
                      I0..*ServiceRequestA request for a service to be performed
                        ... id Σ0..1stringLogical id of this artifactΣ0..1stringLogical 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: CommonLanguages (preferred)
                              Max Binding: AllLanguages: A human language.

                              0..1codeLanguage of the resource content
                              Binding: CommonLanguages (preferred)
                              Max Binding: AllLanguages: A human language.

                                ... 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..*ExtensionExtension
                                    Slice: Unordered, Open by value:url
                                    • Elements differ in short: 'Additional content defined by implementations' vs 'Extension'
                                    • Elements differ in definition: 'May be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.' vs 'An Extension'
                                    ... 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: RequestStatus (required): The status of a service order.

                                                  ?!Σ1..1codedraft | active | on-hold | revoked | completed | entered-in-error | unknown
                                                  Binding: RequestStatus (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: RequestIntent (required): The kind of service request.

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


                                                  Fixed Value: order
                                                  • Elements differ in definition for mustSupport: 'true' vs 'false'
                                                  ... Slices for category SΣ1..*CodeableConceptClassification of service
                                                  Slice: Unordered, Open by pattern:$this
                                                  Binding: ServiceRequestCategoryCodes (example): Classification of the requested service.


                                                  Σ0..*CodeableConceptClassification of service
                                                  Binding: ServiceRequestCategoryCodes (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: RequestPriority (required): Identifies the level of importance to be assigned to actioning the request.

                                                  Σ0..1coderoutine | urgent | asap | stat
                                                  Binding: RequestPriority (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: US Core Procedure Codes (extensible)
                                                      SΣ0..1CodeableConceptWhat is being requested/ordered
                                                      Binding: X12 278 Requested Service Type (required)
                                                      • Element minimum cardinalities differ: '1' vs '0'
                                                      ... orderDetail ΣI0..*CodeableConceptAdditional order information
                                                      Binding: ServiceRequestOrderDetailsCodes (example): Codified order entry details which are based on order context.


                                                      ΣI0..*CodeableConceptAdditional order information
                                                      Binding: ServiceRequestOrderDetailsCodes (example): Codified order entry details which are based on order context.


                                                        ... quantity[x] Σ0..1Quantity, Ratio, RangeService amountSΣ0..1QuantityService amount
                                                        • Elements differ in definition for mustSupport: 'false' vs 'true'
                                                        ... subject SΣ1..1Reference(US Core Patient Profile)Individual or Entity the service is ordered forSΣ1..1Reference(PAS Beneficiary Patient)Individual or Entity the service is ordered for
                                                          ... encounter Σ0..1Reference(Encounter)Encounter in which the request was createdΣ0..1Reference(Encounter)Encounter in which the request was created
                                                            ... occurrence[x] SΣ0..1dateTime S, Period, TimingWhen service should occurS0..1PASTimingA timing schedule that specifies an event that may occur multiple times
                                                            • Elements differ in short: 'When service should occur' vs 'A timing schedule that specifies an event that may occur multiple times'
                                                            • Elements differ in definition: 'The date/time at which the requested service should occur.' vs 'Specifies an event that may occur multiple times. Timing schedules are used to record when things are planned, expected or requested to occur. The most common usage is in dosage instructions for medications. They are also used when planning care of various kinds, and may be used for reporting the schedule to which past regular activities were carried out.'
                                                            ... asNeeded[x] Σ0..1boolean, CodeableConceptPreconditions for service
                                                            Binding: SNOMEDCTMedicationAsNeededReasonCodes (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: SNOMEDCTMedicationAsNeededReasonCodes (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 Related Person | 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: ParticipantRoles (example): Indicates specific responsibility of an individual within the care team, such as "Primary physician", "Team coordinator", "Caregiver", etc.

                                                              Σ0..1CodeableConceptPerformer role
                                                              Binding: ParticipantRoles (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: ServiceDeliveryLocationRoleType (example): A location type where services are delivered.


                                                                  Σ0..*CodeableConceptRequested location
                                                                  Binding: ServiceDeliveryLocationRoleType (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: ProcedureReasonCodes (example): Diagnosis or problem codes justifying the reason for requesting the service investigation.


                                                                      Σ0..*CodeableConceptExplanation/Justification for procedure or service
                                                                      Binding: ProcedureReasonCodes (example): Diagnosis or problem codes justifying the reason for requesting the service investigation.


                                                                        ... reasonReference Σ0..*Reference(Condition | Observation | DiagnosticReport | DocumentReference)Explanation/Justification for service or 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: SNOMEDCTBodyStructures (example): Codes describing anatomical locations. May include laterality.


                                                                                Σ0..*CodeableConceptLocation on Body
                                                                                Binding: SNOMEDCTBodyStructures (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