| Left: | US Core ServiceRequest Profile (http://hl7.org/fhir/us/core/StructureDefinition/us-core-servicerequest) |
| Right: | CRD Service Request (http://hl7.org/fhir/us/davinci-crd/StructureDefinition/profile-servicerequest) |
| Error | StructureDefinition.url | Values for url differ: 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-servicerequest' vs 'http://hl7.org/fhir/us/davinci-crd/StructureDefinition/profile-servicerequest' |
| Error | StructureDefinition.version | Values for version differ: '7.0.0-ballot' vs '2.0.1' |
| Information | StructureDefinition.name | Values for name differ: 'USCoreServiceRequestProfile' vs 'ServiceRequest' |
| Information | StructureDefinition.title | Values for title differ: 'US Core ServiceRequest Profile' vs 'CRD Service Request' |
| Information | StructureDefinition.date | Values for date differ: '2023-10-17' vs '2023-05-30T11:47:53-07:00' |
| Information | StructureDefinition.publisher | Values for publisher differ: 'HL7 International / Cross-Group Projects' vs 'HL7 International / Financial Management' |
| 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: 'Additional content defined by implementations' vs 'Extension' |
| Information | StructureDefinition.definition | Values 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' |
| Warning | ServiceRequest.identifier | Elements differ in definition for mustSupport: 'false' vs 'true' |
| Warning | ServiceRequest.basedOn | Elements differ in definition for mustSupport: 'false' vs 'true' |
| Error | ServiceRequest.basedOn | Type Mismatch: Reference([CanonicalType[http://hl7.org/fhir/StructureDefinition/CarePlan], CanonicalType[http://hl7.org/fhir/StructureDefinition/ServiceRequest], CanonicalType[http://hl7.org/fhir/StructureDefinition/MedicationRequest]]) vs Reference([CanonicalType[http://hl7.org/fhir/us/davinci-crd/StructureDefinition/profile-servicerequest], CanonicalType[http://hl7.org/fhir/us/davinci-crd/StructureDefinition/profile-medicationrequest]]) |
| Warning | ServiceRequest.intent | Elements differ in definition for mustSupport: 'true' vs 'false' |
| Warning | ServiceRequest.category | Elements differ in definition for mustSupport: 'true' vs 'false' |
| Information | StructureDefinition.comment | Values for comment differ: 'In general, only the code and timeframe will be present, though occasional additional qualifiers such as body site or even performer could be included to narrow the scope of the prohibition. If the ServiceRequest.code and ServiceRequest.doNotPerform both contain negation, that will reinforce prohibition and should not have a double negative interpretation.' vs 'In general, only the code and timeframe will be present, though occasional additional qualifiers such as body site or even performer could be included to narrow the scope of the prohibition. If the ServiceRequest.code and ServiceRequest.doNotPerform both contain negation, that will reinforce prohibition and should not have a double negative interpretation. Client systems that do not allow ordering services with 'doNotPerform' of 'true' do not need to add support for this capability. CRD services SHALL understand this element if populated. Typically, 'doNotPerform' orders will not result in coverage-related card responses and might not result in any decision support at all. In some cases, a payer might have documentation or other requirements relating to doNotPerform orders that they wish to communicate.' |
| Warning | ServiceRequest.doNotPerform | Elements differ in definition for mustSupport: 'false' vs 'true' |
| Information | StructureDefinition.short | Values for short differ: 'What is being requested/ordered' vs 'Codes to identify requested services. (CPT, SNOMED CT or LOINC)' |
| Warning | ServiceRequest.quantity[x] | Elements differ in definition for mustSupport: 'false' vs 'true' |
| Warning | ServiceRequest.encounter | Elements differ in definition for mustSupport: 'true' vs 'false' |
| Information | ServiceRequest.authoredOn | Element minimum cardinalities differ: '0' vs '1' |
| Information | ServiceRequest.requester | Element minimum cardinalities differ: '0' vs '1' |
| Warning | ServiceRequest.performer | Elements differ in definition for mustSupport: 'false' vs 'true' |
| Warning | ServiceRequest.locationReference | Elements differ in definition for mustSupport: 'false' vs 'true' |
| Information | ServiceRequest.locationReference | Element maximum cardinalities differ: '2147483647' vs '1' |
| Information | StructureDefinition.short | Values for short differ: '𝗔𝗗𝗗𝗜𝗧𝗜𝗢𝗡𝗔𝗟 𝗨𝗦𝗖𝗗𝗜: Explanation/Justification for procedure or service' vs 'Explanation/Justification for procedure or service' |
| Warning | ServiceRequest.reasonCode | Elements differ in definition for mustSupport: 'false' vs 'true' |
| Information | StructureDefinition.short | Values for short differ: '𝗔𝗗𝗗𝗜𝗧𝗜𝗢𝗡𝗔𝗟 𝗨𝗦𝗖𝗗𝗜: US Core Profile that supports the requested service' vs 'Explanation/Justification for service 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. 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).' vs 'potentially relevant for CRD in some situations.' |
| Warning | ServiceRequest.reasonReference | Elements differ in definition for mustSupport: 'false' vs 'true' |
| 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 | 2023-10-17 | 2023-05-30T11:47:53-07:00 |
|
| 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. | This profile specifies constraints on the ServiceRequest resource to support coverage requirements discovery. |
|
| experimental | false |
| |
| fhirVersion | 4.0.1 | ||
| jurisdiction | |||
 jurisdiction[0] | urn:iso:std:iso:3166#US | ||
| kind | resource | ||
| name | USCoreServiceRequestProfile | ServiceRequest |
|
| publisher | HL7 International / Cross-Group Projects | HL7 International / Financial Management |
|
| purpose | |||
| status | active | ||
| title | US Core ServiceRequest Profile | CRD Service Request |
|
| type | ServiceRequest | ||
| url | http://hl7.org/fhir/us/core/StructureDefinition/us-core-servicerequest | http://hl7.org/fhir/us/davinci-crd/StructureDefinition/profile-servicerequest |
|
| version | 7.0.0-ballot | 2.0.1 |
|
| Name | L Flags | L Card. | L Type | L Description & Constraints | R Flags | R Card. | L Type | L Description & Constraints | Comments | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
 ServiceRequest | C | 0..* | ServiceRequest | A request for a service to be performed | C | 0..* | ServiceRequest | A request for a service to be performed | |||||||||
 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 | Extension Slice: Unordered, Open by value:url | |||||||||||
 modifierExtension | ?! | 0..* | Extension | Extensions that cannot be ignored | ?! | 0..* | Extension | Extensions that cannot be ignored | |||||||||
| identifier | Σ | 0..* | Identifier | Identifiers assigned to this order | SΣ | 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 | SΣ | 0..* | Reference(CRD Service Request | CRD Medication Request) | 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 | 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. Fixed Value: draft | |||||||||
| intent | ?!SΣ | 1..1 | code | proposal | plan | directive | order | original-order | reflex-order | filler-order | instance-order | option Binding: ?? (required): The kind of service request. | ?!Σ | 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 | Classification of service Slice: Unordered, Open by pattern:$this Binding: ?? (example): Classification of the requested service. | Σ | 0..* | CodeableConcept | Classification of service 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 | ?!SΣ | 0..1 | boolean | True if service/procedure should not be performed |
| ||||||||
| code | SΣ | 1..1 | CodeableConcept | What is being requested/ordered Binding: ?? (extensible) | SΣ | 1..1 | CodeableConcept | Codes to identify requested services. (CPT, SNOMED CT or LOINC) Binding: ?? (extensible): Codes describing the type of Service | |||||||||
| 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 | SΣ | 0..1 | Quantity, Ratio, Range | Service amount |
| ||||||||
| subject | SΣ | 1..1 | Reference(US Core Patient Profile S | Group | US Core Location Profile | Device) | Individual or Entity the service is ordered for | SΣ | 1..1 | Reference(CRD Patient) | Individual or Entity the service is ordered for | |||||||||
| encounter | SΣ | 0..1 | Reference(US Core Encounter Profile) | Encounter in which the request was created | Σ | 0..1 | Reference(CRD Encounter) | Encounter in which the request was created |
| ||||||||
| occurrence[x] | SΣ | 0..1 | Period S, dateTime, Timing | When service should occur | SΣ | 0..1 | dateTime, Period, 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 | Date request signed | SΣ | 1..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) | Who/what is requesting service | SΣ | 1..1 | Reference(CRD Practitioner | US Core PractitionerRole Profile) | 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 | SΣ | 0..* | Reference(CRD Practitioner | US Core PractitionerRole Profile) | 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 | SΣ | 0..1 | Reference(CRD Location) | Requested location |
| ||||||||
| reasonCode | Σ | 0..* | CodeableConcept | 𝗔𝗗𝗗𝗜𝗧𝗜𝗢𝗡𝗔𝗟 𝗨𝗦𝗖𝗗𝗜: Explanation/Justification for procedure or service Binding: ?? (extensible) | SΣ | 0..* | CodeableConcept | Explanation/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) | 𝗔𝗗𝗗𝗜𝗧𝗜𝗢𝗡𝗔𝗟 𝗨𝗦𝗖𝗗𝗜: US Core Profile that supports the requested service | SΣ | 0..* | Reference(US Core Condition Profile | US Core Laboratory Result Observation Profile) | Explanation/Justification for service or service |
| ||||||||
| insurance | 0..* | Reference(Coverage | ClaimResponse) | Associated insurance coverage | 0..* | Reference(Coverage | ClaimResponse) | Associated insurance coverage | |||||||||||
| supportingInfo | 0..* | Reference(Resource) | Additional clinical information | 0..* | Reference(Resource) | Additional clinical information | |||||||||||
| specimen | Σ | 0..* | Reference(Specimen) | Procedure Samples | Σ | 0..* | Reference(Specimen) | Procedure Samples | |||||||||
| bodySite | Σ | 0..* | 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 | |||||||||||||||||