abstractbaseDefinitioncopyrightdate- Values Differ
description- Values Differ
experimentalfhirVersionjurisdiction
jurisdiction[0]kindnamepublisher- Values Differ
purposestatustitletypeurlversion- Values Differ
| Left: | US Core ServiceRequest Profile (http://hl7.org/fhir/us/core/StructureDefinition/us-core-servicerequest) |
| Right: | US Core ServiceRequest Profile (http://hl7.org/fhir/us/core/StructureDefinition/us-core-servicerequest) |
| Error | StructureDefinition.version | Values for version differ: '6.1.0' vs '7.0.0' |
| Information | StructureDefinition.date | Values for date differ: '2022-10-07' vs '2023-10-17' |
| Information | StructureDefinition.publisher | Values for publisher differ: 'HL7 International - Cross-Group Projects' vs 'HL7 International / Cross-Group Projects' |
| Information | StructureDefinition.definition | Values for definition differ: '\-' vs 'A record of a request for service such as diagnostic investigations, treatments, or operations to be performed.' |
| Information | StructureDefinition.short | Values 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' |
| Information | StructureDefinition.comment | Values 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.' |
| Information | StructureDefinition.short | Values 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' |
| Information | StructureDefinition.short | Values for short differ: '(USCDI) Classification of service' vs 'Classification of service' |
| Information | StructureDefinition.short | Values for short differ: '(USCDI) What is being requested/ordered' vs 'What is being requested/ordered' |
| Information | StructureDefinition.short | Values for short differ: '(USCDI) Individual or Entity the service is ordered for' vs 'Individual or Entity the service is ordered for' |
| Warning | ServiceRequest.encounter | Elements differ in definition for mustSupport: 'false' vs 'true' |
| Information | StructureDefinition.short | Values for short differ: '(USCDI) When service should occur' vs 'When service should occur' |
| Information | StructureDefinition.short | Values for short differ: '(USCDI) Date request signed' vs 'Date request signed' |
| Information | StructureDefinition.short | Values for short differ: '(USCDI) Who/what is requesting service' vs 'Who/what is requesting service' |
| Information | StructureDefinition.short | Values for short differ: '(USCDI) Explanation/Justification for procedure or service' vs '𝗔𝗗𝗗𝗜𝗧𝗜𝗢𝗡𝗔𝗟 𝗨𝗦𝗖𝗗𝗜: Explanation/Justification for procedure or service' |
| Information | StructureDefinition.comment | Values 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).' |
| Information | StructureDefinition.short | Values for short differ: '(USCDI) US Core Profile that supports the requested service' vs '𝗔𝗗𝗗𝗜𝗧𝗜𝗢𝗡𝗔𝗟 𝗨𝗦𝗖𝗗𝗜: US Core Profile that supports the requested service' |
| Information | StructureDefinition.comment | Values 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).' |
| Information | StructureDefinition.comment | Values 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.' |
| Name | Value | Comments | |
|---|---|---|---|
| abstract | false | ||
| baseDefinition | http://hl7.org/fhir/StructureDefinition/ServiceRequest | ||
| copyright | Used by permission of HL7 International, all rights reserved Creative Commons License | ||
| date | 2022-10-07 | 2023-10-17 |
|
| description | This 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. | The US Core ServiceRequest Profile inherits from the FHIR [ServiceRequest](https://hl7.org/fhir/R4/servicerequest.html) resource; refer to it for scope and usage definitions. This profile sets minimum expectations for recording, searching, and fetching the ServiceRequest information. It specifies which core elements, extensions, vocabularies, and value sets **SHALL** be present and constrains how the elements are used. Providing the floor for standards development for specific use cases promotes interoperability and adoption. |
|
| experimental | |||
| fhirVersion | 4.0.1 | ||
| jurisdiction | |||
| jurisdiction[0] | urn:iso:std:iso:3166#US | ||
| kind | resource | ||
| name | USCoreServiceRequestProfile | ||
| publisher | HL7 International - Cross-Group Projects | HL7 International / Cross-Group Projects |
|
| purpose | |||
| status | active | ||
| title | US Core ServiceRequest Profile | ||
| type | ServiceRequest | ||
| url | http://hl7.org/fhir/us/core/StructureDefinition/us-core-servicerequest | ||
| version | 6.1.0 | 7.0.0 |
|
| Name | L Flags | L Card. | L Type | L Description & Constraints | R Flags | R Card. | R Type | R Description & Constraints | Comments | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
 ServiceRequest | C | 0..* | ServiceRequest | A request for a service to be performed prr-1: orderDetail SHALL only be present if code is present | C | 0..* | ServiceRequest | A request for a service to be performed prr-1: orderDetail SHALL only be present if code is present | |||||||||
 id | Σ | 0..1 | id | Logical id of this artifact | Σ | 0..1 | id | Logical id of this artifact | |||||||||
| meta | Σ | 0..1 | Meta | Metadata about the resource | Σ | 0..1 | Meta | Metadata about the resource | |||||||||
| implicitRules | ?!Σ | 0..1 | uri | A set of rules under which this content was created | ?!Σ | 0..1 | uri | A set of rules under which this content was created | |||||||||
| language | 0..1 | code | Language of the resource content Binding: ?? (preferred): A human language.
| 0..1 | code | Language of the resource content Binding: ?? (preferred): A human language.
| |||||||||||
| text | 0..1 | Narrative | Text summary of the resource, for human interpretation | 0..1 | Narrative | Text summary of the resource, for human interpretation | |||||||||||
| contained | 0..* | Resource | Contained, inline Resources | 0..* | Resource | Contained, inline Resources | |||||||||||
 extension | 0..* | Extension | Additional content defined by implementations | 0..* | Extension | Additional content defined by implementations | |||||||||||
 modifierExtension | ?! | 0..* | Extension | Extensions that cannot be ignored | ?! | 0..* | Extension | Extensions that cannot be ignored | |||||||||
| identifier | Σ | 0..* | Identifier | Identifiers assigned to this order | Σ | 0..* | Identifier | Identifiers 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..* | uri | Instantiates external protocol or definition | Σ | 0..* | uri | Instantiates external protocol or definition | |||||||||
| basedOn | Σ | 0..* | Reference(CarePlan | ServiceRequest | MedicationRequest) | What request fulfills | Σ | 0..* | Reference(CarePlan | ServiceRequest | MedicationRequest) | What request fulfills | |||||||||
| replaces | Σ | 0..* | Reference(ServiceRequest) | What request replaces | Σ | 0..* | Reference(ServiceRequest) | What request replaces | |||||||||
| requisition | Σ | 0..1 | Identifier | Composite Request ID | Σ | 0..1 | Identifier | Composite Request ID | |||||||||
| status | ?!SΣ | 1..1 | code | (USCDI) draft | active | on-hold | revoked | completed | entered-in-error | unknown Binding: ?? (required): The status of a service order. | ?!SΣ | 1..1 | code | draft | active | on-hold | revoked | completed | entered-in-error | unknown Binding: ?? (required): The status of a service order. | |||||||||
| intent | ?!SΣ | 1..1 | code | (USCDI) proposal | plan | directive | order | original-order | reflex-order | filler-order | instance-order | option Binding: ?? (required): The kind of service request. | ?!SΣ | 1..1 | code | proposal | plan | directive | order | original-order | reflex-order | filler-order | instance-order | option Binding: ?? (required): The kind of service request. | |||||||||
| Slices for category | SΣ | 0..* | CodeableConcept | (USCDI) Classification of service Slice: Unordered, Open by pattern:$this Binding: ?? (example): Classification of the requested service. | SΣ | 0..* | CodeableConcept | Classification of service Slice: Unordered, Open by pattern:$this Binding: ?? (example): Classification of the requested service. | |||||||||
| priority | Σ | 0..1 | code | routine | urgent | asap | stat Binding: ?? (required): Identifies the level of importance to be assigned to actioning the request. | Σ | 0..1 | code | routine | urgent | asap | stat Binding: ?? (required): Identifies the level of importance to be assigned to actioning the request. | |||||||||
| doNotPerform | ?!Σ | 0..1 | boolean | True if service/procedure should not be performed | ?!Σ | 0..1 | boolean | True if service/procedure should not be performed | |||||||||
| code | SΣ | 1..1 | CodeableConcept | (USCDI) What is being requested/ordered Binding: ?? (extensible) | SΣ | 1..1 | CodeableConcept | What is being requested/ordered Binding: ?? (extensible) | |||||||||
| orderDetail | ΣC | 0..* | CodeableConcept | Additional order information Binding: ?? (example): Codified order entry details which are based on order context. | ΣC | 0..* | CodeableConcept | Additional order information Binding: ?? (example): Codified order entry details which are based on order context. | |||||||||
| quantity[x] | Σ | 0..1 | Quantity, Ratio, Range | Service amount | Σ | 0..1 | Quantity, Ratio, Range | Service amount | |||||||||
| subject | SΣ | 1..1 | Reference(US Core Patient Profile) | (USCDI) Individual or Entity the service is ordered for | SΣ | 1..1 | Reference(US Core Patient Profile S | Group | US Core Location Profile | Device) | Individual or Entity the service is ordered for | |||||||||
| encounter | Σ | 0..1 | Reference(Encounter) | Encounter in which the request was created | SΣ | 0..1 | Reference(US Core Encounter Profile) | Encounter in which the request was created |
| ||||||||
| occurrence[x] | SΣ | 0..1 | Period S, dateTime, Timing | (USCDI) When service should occur | SΣ | 0..1 | Period S, dateTime, Timing | When service should occur | |||||||||
| asNeeded[x] | Σ | 0..1 | boolean, CodeableConcept | Preconditions 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..1 | boolean, CodeableConcept | Preconditions 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..1 | dateTime | (USCDI) Date request signed | SΣ | 0..1 | dateTime | Date request signed | |||||||||
| requester | SΣ | 0..1 | Reference(US Core Practitioner Profile S | US Core Organization Profile | US Core Patient Profile | PractitionerRole | US Core RelatedPerson Profile | Device) | (USCDI) Who/what is requesting service | SΣ | 0..1 | Reference(US Core Practitioner Profile S | US Core Organization Profile | US Core Patient Profile | PractitionerRole | US Core RelatedPerson Profile | Device) | Who/what is requesting service | |||||||||
| performerType | Σ | 0..1 | CodeableConcept | Performer role Binding: ?? (example): Indicates specific responsibility of an individual within the care team, such as "Primary physician", "Team coordinator", "Caregiver", etc. | Σ | 0..1 | CodeableConcept | Performer 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 | Σ | 0..* | Reference(Practitioner | PractitionerRole | Organization | CareTeam | HealthcareService | Patient | Device | RelatedPerson) | Requested performer | |||||||||
| locationCode | Σ | 0..* | CodeableConcept | Requested location Binding: ?? (example): A location type where services are delivered. | Σ | 0..* | CodeableConcept | Requested location Binding: ?? (example): A location type where services are delivered. | |||||||||
| locationReference | Σ | 0..* | Reference(Location) | Requested location | Σ | 0..* | Reference(Location) | Requested location | |||||||||
| reasonCode | Σ | 0..* | CodeableConcept | (USCDI) Explanation/Justification for procedure or service Binding: ?? (extensible) | Σ | 0..* | CodeableConcept | 𝗔𝗗𝗗𝗜𝗧𝗜𝗢𝗡𝗔𝗟 𝗨𝗦𝗖𝗗𝗜: Explanation/Justification for procedure or service Binding: ?? (extensible) | |||||||||
| reasonReference | Σ | 0..* | Reference(Condition | Observation | DiagnosticReport | DocumentReference) | (USCDI) US Core Profile that supports the requested service | Σ | 0..* | Reference(Condition | Observation | DiagnosticReport | DocumentReference) | 𝗔𝗗𝗗𝗜𝗧𝗜𝗢𝗡𝗔𝗟 𝗨𝗦𝗖𝗗𝗜: US Core Profile that supports the requested service | |||||||||
| insurance | 0..* | Reference(Coverage | ClaimResponse) | Associated insurance coverage | 0..* | Reference(Coverage | ClaimResponse) | Associated insurance coverage | |||||||||||
| supportingInfo | 0..* | Reference(Resource) | Additional clinical information | 0..* | Reference(Resource) | Additional clinical information | |||||||||||
| specimen | Σ | 0..* | Reference(Specimen) | Procedure Samples | Σ | 0..* | Reference(Specimen) | Procedure Samples | |||||||||
| bodySite | Σ | 0..* | CodeableConcept | Location on Body Binding: ?? (example): Codes describing anatomical locations. May include laterality. | Σ | 0..* | CodeableConcept | Location on Body Binding: ?? (example): Codes describing anatomical locations. May include laterality. | |||||||||
| note | 0..* | Annotation | Comments | 0..* | Annotation | Comments | |||||||||||
| patientInstruction | Σ | 0..1 | string | Patient or consumer-oriented instructions | Σ | 0..1 | string | Patient or consumer-oriented instructions | |||||||||
| relevantHistory | 0..* | Reference(Provenance) | Request provenance | 0..* | Reference(Provenance) | Request provenance | |||||||||||
| Documentation for this format | |||||||||||||||||