Profile Comparison between http://hl7.org/fhir/us/core/StructureDefinition/us-core-servicerequest vs http://hl7.org/fhir/us/sdoh-clinicalcare/StructureDefinition/SDOHCC-ServiceRequest

Left:US Core ServiceRequest Profile (http://hl7.org/fhir/us/core/StructureDefinition/us-core-servicerequest)
Right:SDOHCC ServiceRequest (http://hl7.org/fhir/us/sdoh-clinicalcare/StructureDefinition/SDOHCC-ServiceRequest)

Messages

ErrorStructureDefinition.urlValues for url differ: 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-servicerequest' vs 'http://hl7.org/fhir/us/sdoh-clinicalcare/StructureDefinition/SDOHCC-ServiceRequest'
ErrorStructureDefinition.versionValues for version differ: '6.0.0-ballot' vs '2.0.0'
InformationStructureDefinition.nameValues for name differ: 'USCoreServiceRequestProfile' vs 'SDOHCCServiceRequest'
InformationStructureDefinition.titleValues for title differ: 'US Core ServiceRequest Profile' vs 'SDOHCC ServiceRequest'
InformationStructureDefinition.statusValues for status differ: 'active' vs 'draft'
InformationStructureDefinition.dateValues for date differ: '2022-10-07' vs '2020-12-14T04:01:34+00:00'
InformationStructureDefinition.publisherValues for publisher differ: 'HL7 International - Cross-Group Projects' vs 'HL7 International - Patient Care WG'
WarningServiceRequestElements differ in short: 'A request for a service to be performed' vs 'A request for a service to address an SDOH condition, observation or goal.'
WarningServiceRequestElements differ in definition: '\-' vs 'For service requests that address SDOH conditions, observations or goals.'
WarningServiceRequestElements differ in comments: '\-' vs 'Many of the SDOHCC profiles reference one another. One flow supported by this IG is that QuestionnaireResponses result in Observations that can be used as evidence for Conditions that can lead to Goals, ServiceRequests and Procedures. However, alternatives paths are also possible.'
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 comments: '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] for general discussion) or using the [Task] 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] for general discussion) or using the [Task] resource. While all values are currently allowed, there may be a constraint on the values in future releases based on implementation feedback.'
WarningServiceRequest.intentElements differ in comments: 'This element is labeled as a modifier because the intent alters when and how the resource is actually applicable.' vs 'This element is labeled as a modifier because the intent alters when and how the resource is actually applicable. While all values are currently allowed, there may be a contraint on the values in future releases based on implementation feedback.'
WarningServiceRequest.categoryElements differ in definition: 'A code that classifies the service for searching, sorting and display purposes (e.g. 'Surgical Procedure').' vs 'A code that classifies the service for searching, sorting and display purposes (e.g., Education).'
WarningServiceRequest.categoryElements differ in definition for mustSupport: 'true' vs 'false'
InformationServiceRequest.categoryElement minimum cardinalities differ: '1' vs '0'
WarningServiceRequest.priorityElements differ in definition for mustSupport: 'false' vs 'true'
WarningServiceRequest.codeElements differ in short: 'What is being requested/ordered' vs 'What is being requested/ordered.'
WarningServiceRequest.codeElements differ in definition: 'A code that identifies a particular service (i.e., procedure, diagnostic investigation, or panel of investigations) that have been requested.' vs 'A code that identifies a particular service (e.g., procedure) that has been requested.'
WarningServiceRequest.codeElements differ in comments: '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.' vs 'As the Gravity Project continues to refine content for the SDOH categories (e.g., food, housing, transportation, etc.), this value set will be refined to codes that pertain to SDOH categories. For further guidance on external value sets vetted by the Gravity Project see: [SDOH terminology guidance]'
ErrorServiceRequest.subjectType Mismatch: Reference([CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-patient]]) vs Reference([CanonicalType[http://hl7.org/fhir/StructureDefinition/Group], CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-patient], CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-location]])
ErrorServiceRequest.requesterType Mismatch: Reference([CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-practitioner], CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-organization], CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-patient], CanonicalType[http://hl7.org/fhir/StructureDefinition/PractitionerRole], CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-relatedperson], CanonicalType[http://hl7.org/fhir/StructureDefinition/Device]]) vs Reference([CanonicalType[http://hl7.org/fhir/StructureDefinition/RelatedPerson], CanonicalType[http://hl7.org/fhir/StructureDefinition/Device], CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-practitionerrole], CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-practitioner], CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-patient], CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-organization]])
WarningServiceRequest.performerElements differ in definition for mustSupport: 'false' vs 'true'
ErrorServiceRequest.performerType Mismatch: Reference([CanonicalType[http://hl7.org/fhir/StructureDefinition/Practitioner], CanonicalType[http://hl7.org/fhir/StructureDefinition/PractitionerRole], CanonicalType[http://hl7.org/fhir/StructureDefinition/Organization], CanonicalType[http://hl7.org/fhir/StructureDefinition/CareTeam], CanonicalType[http://hl7.org/fhir/StructureDefinition/HealthcareService], CanonicalType[http://hl7.org/fhir/StructureDefinition/Patient], CanonicalType[http://hl7.org/fhir/StructureDefinition/Device], CanonicalType[http://hl7.org/fhir/StructureDefinition/RelatedPerson]]) vs Reference([CanonicalType[http://hl7.org/fhir/StructureDefinition/HealthcareService], CanonicalType[http://hl7.org/fhir/StructureDefinition/Device], CanonicalType[http://hl7.org/fhir/StructureDefinition/RelatedPerson], CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-patient], CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-practitioner], CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-practitionerrole], CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-organization], CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-careteam]])
WarningServiceRequest.reasonCodeElements differ in comments: '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].' 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]. Information represented by ServiceRequest.reasonCode may overlap significantly with information represented by ServiceRequest.reasonReference. Multiple approaches to representing the same information may negatively impact interoperability. Therefore, where similar information could be provided by either ServiceRequest.reasonCode or ServiceRequest.reasonReference, it is recommended that ServiceRequest.reasonReference be used to provide a reason for why a service request was made. As the Gravity Project continues to refine content for the SDOH categories (e.g., food, housing, transportation, etc.), this value set may be refined to codes that pertain to SDOH categories.'
WarningServiceRequest.reasonCodeElements differ in definition for mustSupport: 'true' vs 'false'
WarningServiceRequest.reasonReferenceElements differ in comments: '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].' 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. Additionally, see Comment on reasonCode.'
WarningServiceRequest.reasonReferenceElements differ in definition for mustSupport: 'true' vs 'false'
WarningServiceRequest.supportingInfoElements differ in definition: 'Additional clinical information about the patient or specimen that may influence the services or their interpretations. This information includes diagnosis, clinical findings and other observations. In laboratory ordering these are typically referred to as 'ask at order entry questions (AOEs)'. This includes observations explicitly requested by the producer (filler) to provide context or supporting information needed to complete the order. For example, reporting the amount of inspired oxygen for blood gas measurements.' vs 'Additional clinical information about the patient that may influence the services or their interpretations. This information includes diagnosis, clinical findings and other observations.'
InformationServiceRequest.specimenElement maximum cardinalities differ: '2147483647' vs '0'
InformationServiceRequest.bodySiteElement maximum cardinalities differ: '2147483647' vs '0'

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'
      .date2022-10-072020-12-14T04:01:34+00:00
      • Values Differ
      .descriptionThis profile sets minimum expectations for recording, searching, and fetching the ServiceRequest resource to promote interoperability and adoption through common implementation. It identifies which core elements, extensions, vocabularies, and value sets **SHALL** be present in the resource when using this profile. It provides the floor for standards development for specific use cases.fhirVersion: 4.0.1Profile for service requests that address Social Determinants of Health.
      • Values Differ
      .experimental
        .fhirVersion4.0.1
          .jurisdiction
            ..jurisdiction[0]urn:iso:std:iso:3166#US
              .kindresource
                .nameUSCoreServiceRequestProfileSDOHCCServiceRequest
                • Values Differ
                .publisherHL7 International - Cross-Group ProjectsHL7 International - Patient Care WG
                • Values Differ
                .purpose
                  .statusactivedraft
                  • Values Differ
                  .titleUS Core ServiceRequest ProfileSDOHCC ServiceRequest
                  • Values Differ
                  .typeServiceRequest
                    .urlhttp://hl7.org/fhir/us/core/StructureDefinition/us-core-servicerequesthttp://hl7.org/fhir/us/sdoh-clinicalcare/StructureDefinition/SDOHCC-ServiceRequest
                    • Values Differ
                    .version6.0.0-ballot2.0.0
                    • Values Differ

                    Structure

                    NameL FlagsL Card.L TypeL Description & ConstraintsR FlagsR Card.L TypeL Description & ConstraintsCommentsdoco
                    .. ServiceRequest C0..*ServiceRequestA request for a service to be performed
                    C0..*ServiceRequestA request for a service to address an SDOH condition, observation or goal.
                    • Elements differ in short: 'A request for a service to be performed' vs 'A request for a service to address an SDOH condition, observation or goal.'
                    • Elements differ in definition: '\-' vs 'For service requests that address SDOH conditions, observations or goals.'
                    • Elements differ in comments: '\-' vs 'Many of the SDOHCC profiles reference one another. One flow supported by this IG is that QuestionnaireResponses result in Observations that can be used as evidence for Conditions that can lead to Goals, ServiceRequests and Procedures. However, alternatives paths are also possible.'
                    ... 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: CommonLanguages (preferred): A human language.

                          Additional BindingsPurpose
                          AllLanguagesMax Binding
                          0..1codeLanguage of the resource content
                          Binding: CommonLanguages (preferred): A human language.

                          Additional BindingsPurpose
                          AllLanguagesMax 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..*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)What request fulfills
                                        Slice: Unordered, Open by profile:resolve()
                                          ... 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.

                                              • Elements differ in comments: '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] for general discussion) or using the [Task] 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] for general discussion) or using the [Task] resource. While all values are currently allowed, there may be a constraint on the values in future releases based on implementation feedback.'
                                              ... intent ?!SΣ1..1codeproposal | plan | directive | order | original-order | reflex-order | filler-order | instance-order | option
                                              Binding: RequestIntent (required): The kind of service request.

                                              ?!SΣ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 comments: 'This element is labeled as a modifier because the intent alters when and how the resource is actually applicable.' vs 'This element is labeled as a modifier because the intent alters when and how the resource is actually applicable. While all values are currently allowed, there may be a contraint on the values in future releases based on implementation feedback.'
                                              ... 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
                                              Slice: Unordered, Open by value:$this
                                              Binding: ServiceRequestCategoryCodes (example): Classification of the requested service.


                                              • Elements differ in definition: 'A code that classifies the service for searching, sorting and display purposes (e.g. "Surgical Procedure").' vs 'A code that classifies the service for searching, sorting and display purposes (e.g., Education).'
                                              • 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.

                                              SΣ0..1coderoutine | urgent | asap | stat
                                              Binding: RequestPriority (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: US Core Procedure Codes (extensible)
                                                SΣ1..1CodeableConceptWhat is being requested/ordered.
                                                Binding: US Core Procedure Codes (required): Codes for tests or services that can be carried out by a designated individual, organization or healthcare service.

                                                • Elements differ in short: 'What is being requested/ordered' vs 'What is being requested/ordered.'
                                                • Elements differ in definition: 'A code that identifies a particular service (i.e., procedure, diagnostic investigation, or panel of investigations) that have been requested.' vs 'A code that identifies a particular service (e.g., procedure) that has been requested.'
                                                • Elements differ in comments: '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.' vs 'As the Gravity Project continues to refine content for the SDOH categories (e.g., food, housing, transportation, etc.), this value set will be refined to codes that pertain to SDOH categories. For further guidance on external value sets vetted by the Gravity Project see: [SDOH terminology guidance]'
                                                ... orderDetail ΣC0..*CodeableConceptAdditional order information
                                                Binding: ServiceRequestOrderDetailsCodes (example): Codified order entry details which are based on order context.


                                                ΣC0..*CodeableConceptAdditional order information
                                                Slice: Unordered, Open by pattern:coding
                                                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(Group | US Core Patient Profile | US Core Location Profile)Individual or Entity the service is ordered for
                                                    • Type Mismatch: Reference([CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-patient]]) vs Reference([CanonicalType[http://hl7.org/fhir/StructureDefinition/Group], CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-patient], CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-location]])
                                                    ... 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..1Period S, dateTime, 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Σ0..1dateTimeDate request signed
                                                            ... 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 serviceSΣ0..1Reference(RelatedPerson | Device | US Core PractitionerRole Profile | US Core Practitioner Profile | US Core Patient Profile | US Core Organization Profile)Who/what is requesting service
                                                            • Type Mismatch: Reference([CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-practitioner], CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-organization], CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-patient], CanonicalType[http://hl7.org/fhir/StructureDefinition/PractitionerRole], CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-relatedperson], CanonicalType[http://hl7.org/fhir/StructureDefinition/Device]]) vs Reference([CanonicalType[http://hl7.org/fhir/StructureDefinition/RelatedPerson], CanonicalType[http://hl7.org/fhir/StructureDefinition/Device], CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-practitionerrole], CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-practitioner], CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-patient], CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-organization]])
                                                            ... 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
                                                              SΣ0..*Reference(HealthcareService | Device | RelatedPerson | US Core Patient Profile | US Core Practitioner Profile | US Core PractitionerRole Profile | US Core Organization Profile | US Core CareTeam Profile)Requested performer
                                                              • Elements differ in definition for mustSupport: 'false' vs 'true'
                                                              • Type Mismatch: Reference([CanonicalType[http://hl7.org/fhir/StructureDefinition/Practitioner], CanonicalType[http://hl7.org/fhir/StructureDefinition/PractitionerRole], CanonicalType[http://hl7.org/fhir/StructureDefinition/Organization], CanonicalType[http://hl7.org/fhir/StructureDefinition/CareTeam], CanonicalType[http://hl7.org/fhir/StructureDefinition/HealthcareService], CanonicalType[http://hl7.org/fhir/StructureDefinition/Patient], CanonicalType[http://hl7.org/fhir/StructureDefinition/Device], CanonicalType[http://hl7.org/fhir/StructureDefinition/RelatedPerson]]) vs Reference([CanonicalType[http://hl7.org/fhir/StructureDefinition/HealthcareService], CanonicalType[http://hl7.org/fhir/StructureDefinition/Device], CanonicalType[http://hl7.org/fhir/StructureDefinition/RelatedPerson], CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-patient], CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-practitioner], CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-practitionerrole], CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-organization], CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-careteam]])
                                                              ... 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 SΣ0..*CodeableConceptExplanation/Justification for procedure or service
                                                                  Binding: US Core Condition Code (extensible)
                                                                  Σ0..*CodeableConceptExplanation/Justification for procedure or service
                                                                  Binding: ProcedureReasonCodes (example): Diagnosis or problem codes justifying the reason for requesting the service investigation.


                                                                  • Elements differ in comments: '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].' 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]. Information represented by ServiceRequest.reasonCode may overlap significantly with information represented by ServiceRequest.reasonReference. Multiple approaches to representing the same information may negatively impact interoperability. Therefore, where similar information could be provided by either ServiceRequest.reasonCode or ServiceRequest.reasonReference, it is recommended that ServiceRequest.reasonReference be used to provide a reason for why a service request was made. As the Gravity Project continues to refine content for the SDOH categories (e.g., food, housing, transportation, etc.), this value set may be refined to codes that pertain to SDOH categories.'
                                                                  • Elements differ in definition for mustSupport: 'true' vs 'false'
                                                                  ... reasonReference SΣ0..*Reference(US Core Condition Encounter Diagnosis Profile | US Core Condition Problems and Health Concerns Profile | Observation | US Core DiagnosticReport Profile for Laboratory Results Reporting | US Core DiagnosticReport Profile for Report and Note exchange | US Core DocumentReference Profile)Explanation/Justification for service or service
                                                                  Σ0..*Reference(Condition | Observation | DiagnosticReport | DocumentReference)Explanation/Justification for service or service
                                                                  Slice: Unordered, Open by profile:resolve()
                                                                  • Elements differ in comments: '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].' 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. Additionally, see Comment on reasonCode.'
                                                                  • Elements differ in definition for mustSupport: 'true' vs 'false'
                                                                  ... 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
                                                                    Slice: Unordered, Open by profile:resolve()
                                                                    • Elements differ in definition: 'Additional clinical information about the patient or specimen that may influence the services or their interpretations. This information includes diagnosis, clinical findings and other observations. In laboratory ordering these are typically referred to as "ask at order entry questions (AOEs)". This includes observations explicitly requested by the producer (filler) to provide context or supporting information needed to complete the order. For example, reporting the amount of inspired oxygen for blood gas measurements.' vs 'Additional clinical information about the patient that may influence the services or their interpretations. This information includes diagnosis, clinical findings and other observations.'
                                                                    ... specimen Σ0..*Reference(Specimen)Procedure Samples
                                                                    Σ0..0
                                                                    • Element maximum cardinalities differ: '2147483647' vs '0'
                                                                    ... bodySite Σ0..*CodeableConceptLocation on Body
                                                                    Binding: SNOMEDCTBodyStructures (example): Codes describing anatomical locations. May include laterality.


                                                                    Σ0..0
                                                                    • Element maximum cardinalities differ: '2147483647' vs '0'
                                                                    ... 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