| Left: | CH Lab ServiceRequest: Laboratory Order (http://fhir.ch/ig/ch-lab-report/StructureDefinition/ch-lab-report-servicerequest) |
| Right: | CH LAB ServiceRequest: Laboratory Order (http://fhir.ch/ig/ch-lab-report/StructureDefinition/ch-lab-report-servicerequest) |
| Error | StructureDefinition.version | Values for version differ: '0.1.1' vs '1.0.0-ballot' |
| Information | StructureDefinition.title | Values for title differ: 'CH Lab ServiceRequest: Laboratory Order' vs 'CH LAB ServiceRequest: Laboratory Order' |
| Information | StructureDefinition.date | Values for date differ: '2023-12-28T12:00:19+01:00' vs '2024-05-17T09:31:13+00:00' |
| Information | StructureDefinition.jurisdiction | Removed the item 'urn:iso:std:iso:3166#CHE' |
| Information | StructureDefinition.jurisdiction | Added the item 'urn:iso:std:iso:3166#CH' |
| Information | StructureDefinition.short | Values for short differ: 'CH Lab ServiceRequest: Laboratory Order' vs 'A request for a service to be performed' |
| Information | StructureDefinition.short | Values for short differ: 'Extension' vs 'Additional content defined by implementations' |
| Information | StructureDefinition.definition | Values for definition differ: 'An Extension' vs '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.' |
| Information | ServiceRequest.identifier | Element minimum cardinalities differ: '0' vs '1' |
| Information | StructureDefinition.short | Values for short differ: 'Composite Request ID' vs 'Composite Request ID.' |
| Information | ServiceRequest.code | Example/preferred bindings differ at ServiceRequest.code using binding from ChLabReportServiceRequest |
| Information | StructureDefinition.short | Values for short differ: 'Date request signed' vs 'When the order was placed' |
| Information | StructureDefinition.short | Values for short differ: 'Additional clinical information' vs 'Additional information: e.g AOEs and prior results' |
| Information | StructureDefinition.short | Values for short differ: 'Procedure Samples' vs 'Specimens to be used by the laboratory procedure' |
| 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 'If the specimen information are known when the order is created then the ServiceRequest.specimen should be used. If the ServiceRequest can be updated when the specimen is collected then the ServiceRequest.specimen or the Specimen.request could be used. Otherwise the relationship is recorded in the Specimen.request element' |
| Name | Value | Comments | |
|---|---|---|---|
 abstract | false | ||
| baseDefinition | http://hl7.org/fhir/StructureDefinition/ServiceRequest | ||
| copyright | CC0-1.0 | ||
| date | 2023-12-28T12:00:19+01:00 | 2024-05-17T09:31:13+00:00 |
|
| description | This profile constrains the ServiceRequest resource for the purpose of laboratory orders in Switzerland. | ||
| experimental | |||
| fhirVersion | 4.0.1 | ||
| jurisdiction | |||
 jurisdiction[0] | urn:iso:std:iso:3166#CHE |
| |
 jurisdiction[1] | urn:iso:std:iso:3166#CH |
| |
| kind | resource | ||
| name | ChLabReportServiceRequest | ||
| publisher | HL7 Switzerland | ||
| purpose | |||
| status | active | ||
| title | CH Lab ServiceRequest: Laboratory Order | CH LAB ServiceRequest: Laboratory Order |
|
| type | ServiceRequest | ||
| url | http://fhir.ch/ig/ch-lab-report/StructureDefinition/ch-lab-report-servicerequest | ||
| version | 0.1.1 | 1.0.0-ballot |
|
| 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 Lab ServiceRequest: Laboratory Order prr-1: orderDetail SHALL only be present if code is present ch-lab-sr1: The resource should be conform to the corresponding EU LAB profile code-or-basedOn-required: must have a code for what is beeing requested, or a basedOn element | 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 | |||||||||||
 Slices for extension | 0..* | Extension | Extension Slice: Unordered, Open by value:url | 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 | Σ | 1..* | 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 | ?!Σ | 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): 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 | Σ | 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: ?? (preferred) |
| ||||||||
| 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 Lab Patient) | Individual or Entity the service is ordered for | Σ | 1..1 | Reference(CH LAB Patient | Patient: Animal | Group | Location | Device) | Individual or Entity the service is ordered for | |||||||||
| encounter | Σ | 0..1 | Reference(Encounter) | Encounter in which the request was created | Σ | 0..1 | Reference(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 | When the order was placed | |||||||||
| requester | Σ | 0..1 | Reference(Practitioner | PractitionerRole | Organization | Patient | RelatedPerson | 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: ?? (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(Condition | Observation | DiagnosticReport | DocumentReference) | Explanation/Justification for service or service | Σ | 0..* | Reference(Condition | Observation | DiagnosticReport | DocumentReference) | Explanation/Justification for service or service | |||||||||
| insurance | 0..* | Reference(Coverage | ClaimResponse) | Associated insurance coverage | 0..* | Reference(Coverage) | Associated insurance coverage | |||||||||||
| supportingInfo | 0..* | Reference(Resource) | Additional clinical information | 0..* | Reference(Resource) | Additional information: e.g AOEs and prior results | |||||||||||
| specimen | Σ | 0..* | Reference(CH Lab Specimen: Laboratory) | Procedure Samples | Σ | 0..* | Reference(CH LAB Specimen) | Specimens to be used by the laboratory procedure | |||||||||
| 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 | |||||||||||||||||