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

Left:US Core Service Request (http://hl7.org/fhir/us/core/StructureDefinition/us-core-servicerequest)
Right:QICoreServiceNotRequested (http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-servicenotrequested)

Messages

ErrorStructureDefinition.urlValues for url differ: 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-servicerequest' vs 'http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-servicenotrequested'
ErrorStructureDefinition.versionValues for version differ: '4.1.0' vs '4.1.1'
InformationStructureDefinition.nameValues for name differ: 'USCoreServiceRequest' vs 'QICoreServiceNotRequested'
InformationStructureDefinition.statusValues for status differ: 'active' vs 'draft'
InformationStructureDefinition.publisherValues for publisher differ: 'HL7 International - Cross-Group Projects' vs 'http://www.hl7.org/Special/committees/cqi/index.cfm'
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.modifierExtensionElements differ in short: 'Extensions that cannot be ignored' vs 'Extension'
WarningServiceRequest.modifierExtensionElements differ in definition: 'May be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).' vs 'An Extension'
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'
WarningServiceRequest.doNotPerformElements differ in definition for mustSupport: 'false' vs 'true'
InformationServiceRequest.doNotPerformElement minimum cardinalities differ: '0' vs '1'
WarningServiceRequest.encounterElements differ in definition for mustSupport: 'false' vs 'true'
InformationServiceRequest.authoredOnElement minimum cardinalities differ: '0' vs '1'
WarningServiceRequest.requesterElements differ in definition for mustSupport: 'true' vs 'false'
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'
      .date2018-08-22T00:00:00+00:002018-08-22
        .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 patientNegation profile of ServiceRequest for decision support/quality metrics. Defines the core set of elements and extensions for quality rule and measure authors.
        • Values Differ
        .experimentalfalse
        • Added the item 'false'
        .fhirVersion4.0.1
          .jurisdiction
            ..jurisdiction[0]urn:iso:std:iso:3166#US
              .kindresource
                .nameUSCoreServiceRequestQICoreServiceNotRequested
                • Values Differ
                .publisherHL7 International - Cross-Group Projectshttp://www.hl7.org/Special/committees/cqi/index.cfm
                • Values Differ
                .purpose
                  .statusactivedraft
                  • Values Differ
                  .titleUS Core Service Request
                  • Removed the item 'US Core Service Request'
                  .typeServiceRequest
                    .urlhttp://hl7.org/fhir/us/core/StructureDefinition/us-core-servicerequesthttp://hl7.org/fhir/us/qicore/StructureDefinition/qicore-servicenotrequested
                    • Values Differ
                    .version4.1.04.1.1
                    • 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
                    snr-1: To indicate what service was not requested, either at least one coding in the code or a notDoneValueSet extension shall be provided
                      ... 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..*ExtensionExtension
                                  Slice: Unordered, Open by value:url
                                  • Elements differ in short: 'Extensions that cannot be ignored' vs 'Extension'
                                  • Elements differ in definition: 'May be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).' vs 'An Extension'
                                  ... 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.

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


                                              Fixed Value: completed
                                                ... 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.

                                                • 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?!SΣ1..1booleanTrue if service/procedure should not be performed
                                                  Fixed Value: true
                                                  • 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: US Core Procedure Codes (extensible)
                                                  SΣI1..1CodeableConceptWhat is being requested/ordered
                                                  Binding: US Core Procedure Codes (preferred): Codes describing the Procedure Type

                                                    .... 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..1stringPlain text representation of the conceptΣ0..1stringPlain text representation of the concept
                                                            ... 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 amountΣ0..1Quantity, Ratio, RangeService amount
                                                                ... subject SΣ1..1Reference(US Core Patient Profile)Individual or Entity the service is ordered forSΣ1..1Reference(QICorePatient)Individual or Entity the service is ordered for
                                                                  ... encounter Σ0..1Reference(Encounter)Encounter in which the request was createdSΣ0..1Reference(Encounter)Encounter in which the request was created
                                                                  • Elements differ in definition for mustSupport: 'false' vs 'true'
                                                                  ... occurrence[x] SΣ0..1dateTime S, Period, TimingWhen service should occurSΣ0..1dateTime, Period, TimingWhen service should occur
                                                                    ... 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 signedSΣ1..1dateTimeDate request signed
                                                                      • Element minimum cardinalities differ: '0' vs '1'
                                                                      ... 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(QICorePractitioner | QICorePractitionerRole | QICoreOrganization | QICorePatient | QICoreRelatedPerson | QICoreDevice)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(QICorePractitioner | QICoreOrganization | QICorePatient | QICoreDevice | QICoreRelatedPerson | HealthcareService)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.


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