Left: | CH Core ServiceRequest (http://fhir.ch/ig/ch-core/StructureDefinition/ch-core-servicerequest) |
Right: | CH Core ServiceRequest (http://fhir.ch/ig/ch-core/StructureDefinition/ch-core-servicerequest) |
Error | StructureDefinition.version | Values for version differ: '5.0.0-ballot' vs '5.0.0-ci-build' |
Information | StructureDefinition.date | Values for date differ: '2024-05-16T16:08:37+00:00' vs '2024-11-20T13:11:00+00:00' |
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.' |
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.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 | CC0-1.0 | ||
date | 2024-05-16T16:08:37+00:00 | 2024-11-20T13:11:00+00:00 |
|
description | Base definition of the ServiceRequest resource for use in Swiss specific use cases. | ||
experimental | |||
fhirVersion | 4.0.1 | ||
jurisdiction | |||
jurisdiction[0] | urn:iso:std:iso:3166#CH | ||
kind | resource | ||
name | CHCoreServiceRequest | ||
publisher | HL7 Switzerland | ||
purpose | |||
status | active | ||
title | CH Core ServiceRequest | ||
type | ServiceRequest | ||
url | http://fhir.ch/ig/ch-core/StructureDefinition/ch-core-servicerequest | ||
version | 5.0.0-ballot | 5.0.0-ci-build |
|
Name | L Flags | L Card. | L Type | L Description & Constraints | R Flags | R Card. | R Type | R Description & Constraints | Comments | ||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
ServiceRequest | C | 0..* | ServiceRequest | CH Core ServiceRequest prr-1: orderDetail SHALL only be present if code is present | C | 0..* | ServiceRequest | CH Core ServiceRequest 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 | CH Core ServiceRequest | CH Core MedicationRequest) | What request fulfills | Σ | 0..* | Reference(CarePlan | CH Core ServiceRequest | CH Core 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 | ?!Σ | 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 | ?!Σ | 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. | |||||||||
category | Σ | 0..* | CodeableConcept | Classification of service Binding: ?? (example) | Σ | 0..* | CodeableConcept | Classification of service Binding: ?? (example) | |||||||||
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 | Σ | 0..1 | CodeableConcept | What is being requested/ordered Binding: ?? (example): Codes for tests or services that can be carried out by a designated individual, organization or healthcare service. For laboratory, LOINC is (preferred)[http://build.fhir.org/terminologies.html#preferred] and a valueset using LOINC Order codes is available here. | Σ | 0..1 | CodeableConcept | What is being requested/ordered Binding: ?? (example): Codes for tests or services that can be carried out by a designated individual, organization or healthcare service. For laboratory, LOINC is preferred and a valueset using LOINC Order codes is available here. | |||||||||
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 | Σ | 1..1 | Reference(CH Core Patient | Group | CH Core Location | Device) | Individual or Entity the service is ordered for | Σ | 1..1 | Reference(CH Core Patient | Group | CH Core Location | Device) | Individual or Entity the service is ordered for | |||||||||
encounter | Σ | 0..1 | Reference(CH Core Encounter) | Encounter in which the request was created | Σ | 0..1 | Reference(CH Core Encounter) | Encounter in which the request was created | |||||||||
occurrence[x] | Σ | 0..1 | dateTime, Period, Timing | When service should occur | Σ | 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 | Σ | 0..1 | dateTime | Date request signed | Σ | 0..1 | dateTime | Date request signed | |||||||||
requester | Σ | 0..1 | Reference(CH Core Practitioner | CH Core PractitionerRole | CH Core Organization | CH Core Patient | RelatedPerson | Device) | Who/what is requesting service | Σ | 0..1 | Reference(CH Core Practitioner | CH Core PractitionerRole | CH Core Organization | CH Core 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(CH Core Practitioner | CH Core PractitionerRole | CH Core Organization | CareTeam | HealthcareService | CH Core Patient | Device | RelatedPerson) | Requested performer | Σ | 0..* | Reference(CH Core Practitioner | CH Core PractitionerRole | CH Core Organization | CareTeam | HealthcareService | CH Core 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: ?? (example): Diagnosis or problem codes justifying the reason for requesting the service investigation. | Σ | 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(CH Core Condition | Observation | DiagnosticReport | CH Core DocumentReference) | Explanation/Justification for service or service | Σ | 0..* | Reference(CH Core Condition | Observation | DiagnosticReport | CH Core DocumentReference) | Explanation/Justification for service or service | |||||||||
insurance | 0..* | Reference(CH Core Coverage | ClaimResponse) | Associated insurance coverage | 0..* | Reference(CH Core 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 |