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

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

Messages

ErrorStructureDefinition.urlValues for url differ: 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-servicerequest' vs 'http://hl7.org/fhir/us/eltss/StructureDefinition/ServiceRequest-eltss'
ErrorStructureDefinition.versionValues for version differ: '6.1.0' vs '2.0.0-ballot'
InformationStructureDefinition.nameValues for name differ: 'USCoreServiceRequestProfile' vs 'ServiceRequest_eltss'
InformationStructureDefinition.dateValues for date differ: '2022-10-07' vs '2019-02-17T00:00:00-05:00'
InformationStructureDefinition.publisherValues for publisher differ: 'HL7 International - Cross-Group Projects' vs 'HL7 International / Human and Social Services'
InformationStructureDefinition.definitionValues for definition differ: '\-' vs 'A record of a request for service such as diagnostic investigations, treatments, or operations to be performed.'
InformationStructureDefinition.shortValues for short differ: 'Additional content defined by implementations' vs 'Extension'
InformationStructureDefinition.definitionValues for definition differ: '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'
InformationStructureDefinition.shortValues for short differ: '(USCDI) draft | active | on-hold | revoked | completed | entered-in-error | unknown' vs 'draft | active | on-hold | revoked | completed | entered-in-error | unknown'
InformationStructureDefinition.commentValues for comment differ: '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](http://hl7.org/fhir/R4/event.html) for general discussion) or using the [Task](http://hl7.org/fhir/R4/task.html) 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](event.html) for general discussion) or using the [Task](task.html) resource.'
WarningServiceRequest.statusElements differ in definition for mustSupport: 'true' vs 'false'
InformationStructureDefinition.shortValues for short differ: '(USCDI) proposal | plan | directive | order | original-order | reflex-order | filler-order | instance-order | option' vs 'proposal | plan | directive | order | original-order | reflex-order | filler-order | instance-order | option'
WarningServiceRequest.intentElements differ in definition for mustSupport: 'true' vs 'false'
InformationStructureDefinition.shortValues for short differ: '(USCDI) Classification of service' vs 'Classification of service'
WarningServiceRequest.categoryElements differ in definition for mustSupport: 'true' vs 'false'
InformationStructureDefinition.shortValues for short differ: '(USCDI) What is being requested/ordered' vs 'Service Name'
InformationStructureDefinition.definitionValues for definition differ: 'A code that identifies a particular service (i.e., procedure, diagnostic investigation, or panel of investigations) that have been requested.' vs 'Identifies the paid and/or non-paid service provided to a person. Include the code and display name plus any modifiers when a coding system (e.g., Healthcare Common Procedure Coding System (HCPCS), Home Health Revenue Codes) is used.'
InformationStructureDefinition.commentValues for comment differ: '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 'Use HCPCS (https://www.cms.gov/Medicare/Coding/MedHCPCSGenInfo/) code + modifiers or free text.'
InformationServiceRequest.codeElement minimum cardinalities differ: '1' vs '0'
InformationStructureDefinition.shortValues for short differ: 'Service amount' vs 'Service Unit Quantity + Unit Type + Time Interval'
InformationStructureDefinition.definitionValues for definition differ: 'An amount of service being requested which can be a quantity ( for example $1,500 home modification), a ratio ( for example, 20 half day visits per month), or a range (2.0 to 1.8 Gy per fraction).' vs 'The numerical amount/unit or Interval of the service unit being provided.'
WarningServiceRequest.quantity[x]Elements differ in definition for mustSupport: 'false' vs 'true'
InformationStructureDefinition.shortValues for short differ: '(USCDI) Individual or Entity the service is ordered for' vs 'Individual or Entity the service is ordered for'
InformationStructureDefinition.shortValues for short differ: '(USCDI) When service should occur' vs 'Service Start + End Date'
InformationStructureDefinition.definitionValues for definition differ: 'The date/time at which the requested service should occur.' vs 'The start and end date of the service being provided.'
InformationStructureDefinition.shortValues for short differ: '(USCDI) Date request signed' vs 'Date request signed'
InformationStructureDefinition.shortValues for short differ: '(USCDI) Who/what is requesting service' vs 'Who/what is requesting service'
InformationStructureDefinition.shortValues for short differ: 'Requested performer' vs 'Service Provider Name + Phone + Relationship'
InformationStructureDefinition.definitionValues for definition differ: 'The desired performer for doing the requested service. For example, the surgeon, dermatopathologist, endoscopist, etc.' vs 'The entity or individual providing the service. For paid services use the organization/agency name, for non-paid services use the first and last name of the individual providing the service.'
WarningServiceRequest.performerElements differ in definition for mustSupport: 'false' vs 'true'
InformationStructureDefinition.shortValues for short differ: 'Requested location' vs 'Service Delivery Address'
InformationStructureDefinition.definitionValues for definition differ: 'A reference to the the preferred location(s) where the procedure should actually happen. E.g. at home or nursing day care center.' vs 'The address where service delivery will take place if service will not be provided at the person's address.'
WarningServiceRequest.locationReferenceElements differ in definition for mustSupport: 'false' vs 'true'
InformationStructureDefinition.shortValues for short differ: '(USCDI) Explanation/Justification for procedure or service' vs 'Explanation/Justification for procedure or service'
InformationStructureDefinition.commentValues for comment differ: '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](http://hl7.org/fhir/R4/servicerequest-example-di.html).' 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](servicerequest-example-di.html).'
InformationStructureDefinition.shortValues for short differ: '(USCDI) US Core Profile that supports the requested service' vs 'Explanation/Justification for service or service'
InformationStructureDefinition.commentValues for comment differ: '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](http://hl7.org/fhir/R4/servicerequest-example-di.html).' 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 as shown in the [CT Scan example](servicerequest-example-di.html).'
InformationStructureDefinition.shortValues for short differ: 'Associated insurance coverage' vs 'Service Funding Source'
InformationStructureDefinition.definitionValues for definition differ: 'Insurance plans, coverage extensions, pre-authorizations and/or pre-determinations that may be needed for delivering the requested service.' vs 'The source of payment for the service.'
WarningServiceRequest.insuranceElements differ in definition for mustSupport: 'false' vs 'true'
WarningServiceRequest.supportingInfoElements differ in definition for mustSupport: 'false' vs 'true'
InformationStructureDefinition.commentValues for comment differ: 'Many diagnostic procedures need a specimen, but the request itself is not actually about the specimen. This element is for when the diagnostic is requested on already existing specimens and the request points to the specimen it applies to. Conversely, if the request is entered first with an unknown specimen, then the [Specimen](http://hl7.org/fhir/R4/specimen.html) resource points to the ServiceRequest.' vs 'Many diagnostic procedures need a specimen, but the request itself is not actually about the specimen. This element is for when the diagnostic is requested on already existing specimens and the request points to the specimen it applies to. Conversely, if the request is entered first with an unknown specimen, then the [Specimen](specimen.html) resource points to the ServiceRequest.'
InformationStructureDefinition.shortValues for short differ: 'Comments' vs 'Service Comment'
InformationStructureDefinition.definitionValues for definition differ: 'Any other notes and comments made about the service request. For example, internal billing notes.' vs 'Additional information related to the service being provided. This field could capture additional information of the frequency of the service, how the person wants the service delivered and only used when the comment provides additional detail of the service not already handled by another element.'
WarningServiceRequest.noteElements 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'
      .date2022-10-072019-02-17T00:00:00-05: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 and constrains the way the elements are used when using this profile. It provides the floor for standards development for specific use cases.ServiceRequest resource mapping for eLTSS
      • Values Differ
      .experimentalfalse
      • Added the item 'false'
      .fhirVersion4.0.1
        .jurisdiction
          ..jurisdiction[0]urn:iso:std:iso:3166#US
            .kindresource
              .nameUSCoreServiceRequestProfileServiceRequest_eltss
              • Values Differ
              .publisherHL7 International - Cross-Group ProjectsHL7 International / Human and Social Services
              • Values Differ
              .purpose
                .statusactive
                  .titleUS Core ServiceRequest Profile
                  • Removed the item 'US Core ServiceRequest Profile'
                  .typeServiceRequest
                    .urlhttp://hl7.org/fhir/us/core/StructureDefinition/us-core-servicerequesthttp://hl7.org/fhir/us/eltss/StructureDefinition/ServiceRequest-eltss
                    • Values Differ
                    .version6.1.02.0.0-ballot
                    • 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 be performed
                      ... id Σ0..1idLogical id of this artifactΣ0..1idLogical id of this artifact
                        ... meta Σ0..1MetaMetadata about the resourceΣ0..1MetaMetadata about the resource
                          ... implicitRules ?!Σ0..1uriA set of rules under which this content was created?!Σ0..1uriA set of rules under which this content was created
                            ... language 0..1codeLanguage of the resource content
                            Binding: ?? (preferred): A human language.

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

                            Additional BindingsPurpose
                            ??Max Binding
                              ... text 0..1NarrativeText summary of the resource, for human interpretation0..1NarrativeText summary of the resource, for human interpretation
                                ... contained 0..*ResourceContained, inline Resources
                                0..*ResourceContained, inline Resources
                                  ... extension 0..*ExtensionAdditional content defined by implementations
                                  0..*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
                                            ... basedOn Σ0..*Reference(CarePlan | ServiceRequest | MedicationRequest)What request fulfills
                                            Σ0..*Reference(CarePlan_eltss | ServiceRequest_eltss | MedicationRequest)What request fulfills
                                              ... replaces Σ0..*Reference(ServiceRequest)What request replaces
                                              Σ0..*Reference(ServiceRequest_eltss)What request replaces
                                                ... requisition Σ0..1IdentifierComposite Request IDΣ0..1IdentifierComposite Request ID
                                                  ... status ?!SΣ1..1code(USCDI) draft | active | on-hold | revoked | completed | entered-in-error | unknown
                                                  Binding: ?? (required): The status of a service order.

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

                                                  • Elements differ in definition for mustSupport: 'true' vs 'false'
                                                  ... intent ?!SΣ1..1code(USCDI) proposal | plan | directive | order | original-order | reflex-order | filler-order | instance-order | option
                                                  Binding: ?? (required): The kind of service request.

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

                                                  • Elements differ in definition for mustSupport: 'true' vs 'false'
                                                  ... Slices for category SΣ0..*CodeableConcept(USCDI) Classification of service
                                                  Slice: Unordered, Open by pattern:$this
                                                  Binding: ?? (example): Classification of the requested service.


                                                  Σ0..*CodeableConceptClassification of service
                                                  Binding: ?? (example): Classification of the requested service.


                                                  • Elements differ in definition for mustSupport: 'true' vs 'false'
                                                  ... priority Σ0..1coderoutine | urgent | asap | stat
                                                  Binding: ?? (required): Identifies the level of importance to be assigned to actioning the request.

                                                  Σ0..1coderoutine | urgent | asap | stat
                                                  Binding: ?? (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..1CodeableConcept(USCDI) What is being requested/ordered
                                                      Binding: ?? (extensible)
                                                      SΣ0..1CodeableConceptService Name
                                                      Binding: ?? (preferred): Use HCPCS (https://www.cms.gov/Medicare/Coding/MedHCPCSGenInfo/) code + modifiers or free text.

                                                      • Element minimum cardinalities differ: '1' vs '0'
                                                      .... id 0..1stringUnique id for inter-element referencing
                                                      • Added this element
                                                      .... Slices for extension 0..*ExtensionAdditional content defined by implementations
                                                      Slice: Unordered, Open by value:url
                                                      • Added this element
                                                      .... coding SΣ0..*CodingCode defined by a terminology system
                                                      • Added this element
                                                      .... text SΣ0..1stringPlain text representation of the concept
                                                      • Added this element
                                                      ... orderDetail ΣC0..*CodeableConceptAdditional order information
                                                      Binding: ?? (example): Codified order entry details which are based on order context.


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


                                                        ... quantity[x] Σ0..1Quantity, Ratio, RangeService amountSΣ0..1Quantity, Ratio, RangeService Unit Quantity + Unit Type + Time Interval
                                                        Slice: Unordered, Open by type:$this
                                                        • Elements differ in definition for mustSupport: 'false' vs 'true'
                                                        ... subject SΣ1..1Reference(US Core Patient Profile)(USCDI) Individual or Entity the service is ordered forSΣ1..1Reference(Patient_eltss S | Group | US Core Implantable Device Profile | Device | Location_eltss)Individual or Entity the service is ordered for
                                                          ... encounter Σ0..1Reference(Encounter)Encounter in which the request was createdΣ0..1Reference(US Core Encounter Profile)Encounter in which the request was created
                                                            ... occurrence[x] SΣ0..1Period S, dateTime, Timing(USCDI) When service should occurSΣ0..1dateTime, Period, TimingService Start + End Date
                                                            Slice: Unordered, Open by type:$this
                                                              ... asNeeded[x] Σ0..1boolean, CodeableConceptPreconditions for service
                                                              Binding: ?? (example): A coded concept identifying the pre-condition that should hold prior to performing a procedure. For example "pain", "on flare-up", etc.

                                                              Σ0..1boolean, CodeableConceptPreconditions for service
                                                              Binding: ?? (example): A coded concept identifying the pre-condition that should hold prior to performing a procedure. For example "pain", "on flare-up", etc.

                                                                ... authoredOn SΣ0..1dateTime(USCDI) Date 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)(USCDI) Who/what is requesting serviceSΣ0..1Reference(Practitioner_eltss S | eLTSS PractitionerRole Profile | Patient_eltss | US Core Organization Profile | eLTSS RelatedPerson Profile | US Core Implantable Device Profile | Device)Who/what is requesting service
                                                                    ... performerType Σ0..1CodeableConceptPerformer role
                                                                    Binding: ?? (example): Indicates specific responsibility of an individual within the care team, such as "Primary physician", "Team coordinator", "Caregiver", etc.

                                                                    Σ0..1CodeableConceptPerformer role
                                                                    Binding: ?? (example): Indicates specific responsibility of an individual within the care team, such as "Primary physician", "Team coordinator", "Caregiver", etc.

                                                                      ... performer Σ0..*Reference(Practitioner | PractitionerRole | Organization | CareTeam | HealthcareService | Patient | Device | RelatedPerson)Requested performer
                                                                      SΣ0..*Reference(Practitioner_eltss S | eLTSS PractitionerRole Profile S | Patient_eltss S | US Core Organization Profile S | eLTSS RelatedPerson Profile S | US Core Implantable Device Profile | Device | US Core CareTeam Profile | HealthcareService)Service Provider Name + Phone + Relationship
                                                                      • Elements differ in definition for mustSupport: 'false' vs 'true'
                                                                      ... locationCode Σ0..*CodeableConceptRequested location
                                                                      Binding: ?? (example): A location type where services are delivered.


                                                                      Σ0..*CodeableConceptRequested location
                                                                      Binding: ?? (example): A location type where services are delivered.


                                                                        ... locationReference Σ0..*Reference(Location)Requested location
                                                                        SΣ0..*Reference(Location_eltss)Service Delivery Address
                                                                        • Elements differ in definition for mustSupport: 'false' vs 'true'
                                                                        ... reasonCode Σ0..*CodeableConcept(USCDI) Explanation/Justification for procedure or service
                                                                        Binding: ?? (extensible)
                                                                        Σ0..*CodeableConceptExplanation/Justification for procedure or service
                                                                        Binding: ?? (example): Diagnosis or problem codes justifying the reason for requesting the service investigation.


                                                                          ... reasonReference Σ0..*Reference(Condition | Observation | DiagnosticReport | DocumentReference)(USCDI) US Core Profile that supports the requested service
                                                                          Σ0..*Reference(Condition_eltss | Observation_eltss | US Core DiagnosticReport Profile for Report and Note exchange | US Core DocumentReference Profile)Explanation/Justification for service or service
                                                                            ... insurance 0..*Reference(Coverage | ClaimResponse)Associated insurance coverage
                                                                            S0..*Reference(Coverage S | ClaimResponse)Service Funding Source
                                                                            • Elements differ in definition for mustSupport: 'false' vs 'true'
                                                                            ... supportingInfo 0..*Reference(Resource)Additional clinical information
                                                                            S0..*Reference(Resource)Additional clinical information
                                                                            • Elements differ in definition for mustSupport: 'false' vs 'true'
                                                                            ... specimen Σ0..*Reference(Specimen)Procedure Samples
                                                                            Σ0..*Reference(Specimen)Procedure Samples
                                                                              ... bodySite Σ0..*CodeableConceptLocation on Body
                                                                              Binding: ?? (example): Codes describing anatomical locations. May include laterality.


                                                                              Σ0..*CodeableConceptLocation on Body
                                                                              Binding: ?? (example): Codes describing anatomical locations. May include laterality.


                                                                                ... note 0..*AnnotationComments
                                                                                S0..*AnnotationService Comment
                                                                                • Elements differ in definition for mustSupport: 'false' vs 'true'
                                                                                ... 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