| Left: | US Core ServiceRequest Profile (http://hl7.org/fhir/us/core/StructureDefinition/us-core-servicerequest) |
| Right: | PAS Service Request (http://hl7.org/fhir/us/davinci-pas/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-pas/StructureDefinition/profile-servicerequest' |
| Error | StructureDefinition.version | Values for version differ: '7.0.0' vs '2.1.0-preview' |
| Information | StructureDefinition.name | Values for name differ: 'USCoreServiceRequestProfile' vs 'PASServiceRequest' |
| Information | StructureDefinition.title | Values for title differ: 'US Core ServiceRequest Profile' vs 'PAS Service Request' |
| Information | StructureDefinition.date | Values for date differ: '2023-10-17' vs '2024-11-14T15:41:07+00:00' |
| Information | StructureDefinition.publisher | Values for publisher differ: 'HL7 International / Cross-Group Projects' vs 'HL7 International / Financial Management' |
| 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' |
| 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](event.html) for general discussion) or using the [Task](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](http://hl7.org/fhir/R4/event.html) for general discussion) or using the [Task](http://hl7.org/fhir/R4/task.html) resource.' |
| Warning | ServiceRequest.status | Elements differ in definition for mustSupport: 'true' vs 'false' |
| Warning | ServiceRequest.category | Elements differ in definition for mustSupport: 'true' vs 'false' |
| Information | ServiceRequest.code | Element minimum cardinalities differ: '1' vs '0' |
| 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 | StructureDefinition.short | Values for short differ: 'When service should occur' vs 'A timing schedule that specifies an event that may occur multiple times' |
| Information | StructureDefinition.definition | Values for definition differ: 'The date/time at which the requested service should occur.' vs 'Specifies an event that may occur multiple times. Timing schedules are used to record when things are planned, expected or requested to occur. The most common usage is in dosage instructions for medications. They are also used when planning care of various kinds, and may be used for reporting the schedule to which past regular activities were carried out.' |
| Warning | ServiceRequest.authoredOn | Elements differ in definition for mustSupport: 'true' vs 'false' |
| Warning | ServiceRequest.requester | Elements differ in definition for mustSupport: 'true' vs 'false' |
| Information | StructureDefinition.short | Values for short differ: '𝗔𝗗𝗗𝗜𝗧𝗜𝗢𝗡𝗔𝗟 𝗨𝗦𝗖𝗗𝗜: 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](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](http://hl7.org/fhir/R4/servicerequest-example-di.html).' |
| 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 '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).' |
| 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](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](http://hl7.org/fhir/R4/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 | 2023-10-17 | 2024-11-14T15:41:07+00:00 |
|
| description | 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. | PAS constraints on ServiceRequest resource mandating support for elements relevant to the generic services being requested on a prior authorization request |
|
| experimental | |||
| fhirVersion | 4.0.1 | ||
| jurisdiction | |||
 jurisdiction[0] | urn:iso:std:iso:3166#US | ||
| kind | resource | ||
| name | USCoreServiceRequestProfile | PASServiceRequest |
|
| publisher | HL7 International / Cross-Group Projects | HL7 International / Financial Management |
|
| purpose | |||
| status | active | ||
| title | US Core ServiceRequest Profile | PAS Service Request |
|
| type | ServiceRequest | ||
| url | http://hl7.org/fhir/us/core/StructureDefinition/us-core-servicerequest | http://hl7.org/fhir/us/davinci-pas/StructureDefinition/profile-servicerequest |
|
| version | 7.0.0 | 2.1.0-preview |
|
| 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 | 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 | Σ | 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 | draft | active | on-hold | revoked | completed | entered-in-error | unknown Binding: ?? (required): The status of a service order. | ?!Σ | 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 | 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. Fixed Value: order | |||||||||
| 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 | ?!Σ | 0..1 | boolean | True if service/procedure should not be performed | |||||||||
| code | SΣ | 1..1 | CodeableConcept | What is being requested/ordered Binding: ?? (extensible) | SΣ | 0..1 | CodeableConcept | What is being requested/ordered Binding: ?? (required) |
| ||||||||
| 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 | Service amount |
| ||||||||
| subject | SΣ | 1..1 | Reference(US Core Patient Profile(7.0.0) S | Group | US Core Location Profile(7.0.0) | Device) | Individual or Entity the service is ordered for | SΣ | 1..1 | Reference(PAS Beneficiary Patient) | Individual or Entity the service is ordered for | |||||||||
| encounter | SΣ | 0..1 | Reference(US Core Encounter Profile(7.0.0)) | Encounter in which the request was created | Σ | 0..1 | Reference(Encounter) | Encounter in which the request was created |
| ||||||||
| occurrence[x] | SΣ | 0..1 | Period S, dateTime, Timing | When service should occur | S | 0..1 | ?? | A timing schedule that specifies an event that may occur multiple times | |||||||||
| 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 | Σ | 0..1 | dateTime | Date request signed |
| ||||||||
| requester | SΣ | 0..1 | Reference(US Core Practitioner Profile(7.0.0) S | US Core Organization Profile(7.0.0) | US Core Patient Profile(7.0.0) | PractitionerRole | US Core RelatedPerson Profile(7.0.0) | Device) | Who/what is requesting service | Σ | 0..1 | Reference(Practitioner | PractitionerRole | Organization | Patient | RelatedPerson | 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 | 𝗔𝗗𝗗𝗜𝗧𝗜𝗢𝗡𝗔𝗟 𝗨𝗦𝗖𝗗𝗜: Explanation/Justification for procedure or service Binding: ?? (extensible) | Σ | 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 | Σ | 0..* | Reference(Condition | Observation | DiagnosticReport | DocumentReference) | 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 | |||||||||||||||||