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

Left:SDOHCC ServiceRequest (http://hl7.org/fhir/us/sdoh-clinicalcare/StructureDefinition/SDOHCC-ServiceRequest)
Right:SDOHCC ServiceRequest (http://hl7.org/fhir/us/sdoh-clinicalcare/StructureDefinition/SDOHCC-ServiceRequest)

Messages

ErrorStructureDefinition.versionValues for version differ: '1.0.0' vs '2.0.0'
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. While all values are currently allowed, there may be a constraint on the values in future releases based on implementation feedback.' 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.codeElements differ in comments: '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.' 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]'
WarningServiceRequest.authoredOnElements differ in definition for mustSupport: 'false' vs 'true'
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]. Additionally, see Comment on reasonCode.' 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.'

Metadata

NameValueComments
.abstractfalse
    .baseDefinitionhttp://hl7.org/fhir/StructureDefinition/ServiceRequest
      .copyright
        .date2020-12-14T04:01:34+00:00
          .descriptionThis profile constrains the ServiceRequest resource for requests that address Social Determinants of Health.Profile 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
                    .nameSDOHCCServiceRequest
                      .publisherHL7 International - Patient Care WG
                        .purpose
                          .statusdraft
                            .titleSDOHCC ServiceRequest
                              .typeServiceRequest
                                .urlhttp://hl7.org/fhir/us/sdoh-clinicalcare/StructureDefinition/SDOHCC-ServiceRequest
                                  .version1.0.02.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 address an SDOH condition, observation or goal.
                                  C0..*ServiceRequestA request for a service to address an SDOH condition, observation or goal.
                                    ... id Σ0..1stringLogical 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
                                                ... Slices for extension 0..*ExtensionExtension
                                                Slice: Unordered, Open by value:url
                                                0..*ExtensionExtension
                                                Slice: Unordered, Open by value:url
                                                  ... 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
                                                          ... Slices for basedOn Σ0..*Reference(CarePlan | ServiceRequest)What request fulfills
                                                          Slice: Unordered, Open by profile:resolve()
                                                          Σ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. While all values are currently allowed, there may be a constraint on the values in future releases based on implementation feedback.' 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.

                                                                  ... Slices for category Σ0..*CodeableConceptClassification of service
                                                                  Slice: Unordered, Open by value:$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.


                                                                    ... priority SΣ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.

                                                                      ... 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: SDOHCCValueSetSNOMEDCTCPTLOINCHCPCSII (preferred): Codes for tests or services that can be carried out by a designated individual, organization or healthcare service.

                                                                        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 comments: '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.' 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(Group | US Core Patient Profile | US Core Location 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
                                                                              ... 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, 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 Σ0..1dateTimeDate request signedSΣ0..1dateTimeDate request signed
                                                                                    • Elements differ in definition for mustSupport: 'false' vs 'true'
                                                                                    ... requester SΣ0..1Reference(RelatedPerson | Device | US Core PractitionerRole Profile | US Core Practitioner Profile | US Core Patient Profile | US Core Organization Profile)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
                                                                                      ... 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 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
                                                                                        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
                                                                                          ... locationCode Σ0..*CodeableConceptRequested location
                                                                                          Binding: V3 Value SetServiceDeliveryLocationRoleType (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.


                                                                                                ... Slices for reasonReference Σ0..*Reference(Condition | Observation | DiagnosticReport | DocumentReference)Explanation/Justification for service or service
                                                                                                Slice: Unordered, Open by profile:resolve()
                                                                                                Σ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]. Additionally, see Comment on reasonCode.' 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.'
                                                                                                ... insurance 0..*Reference(Coverage | ClaimResponse)Associated insurance coverage
                                                                                                0..*Reference(Coverage | ClaimResponse)Associated insurance coverage
                                                                                                  ... Slices for supportingInfo 0..*Reference(Resource)Additional clinical information
                                                                                                  Slice: Unordered, Open by profile:resolve()
                                                                                                  0..*Reference(Resource)Additional clinical information
                                                                                                  Slice: Unordered, Open by profile:resolve()
                                                                                                    ... specimen Σ0..0Σ0..0
                                                                                                      ... bodySite Σ0..0Σ0..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