abstractbaseDefinition- Values Differ
copyrightdate- Values Differ
descriptionexperimentalfhirVersionjurisdiction
jurisdiction[0]kindnamepublisherpurposestatus- Values Differ
titletypeurlversion- Values Differ
| Left: | CH ELM ServiceRequest: Laboratory Order (http://fhir.ch/ig/ch-elm/StructureDefinition/ch-elm-servicerequest-laboratory-order) |
| Right: | CH ELM ServiceRequest: Laboratory Order (http://fhir.ch/ig/ch-elm/StructureDefinition/ch-elm-servicerequest-laboratory-order) |
| Error | StructureDefinition.version | Values for version differ: '1.0.0-trialuse' vs '1.1.0' |
| Information | StructureDefinition.status | Values for status differ: 'draft' vs 'active' |
| Information | StructureDefinition.date | Values for date differ: '2023-09-13T14:45:41+02:00' vs '2024-01-31T12:55:13+01:00' |
| Error | StructureDefinition.baseDefinition | Values for baseDefinition differ: 'http://fhir.ch/ig/ch-lab-report/StructureDefinition/ch-lab-servicerequest-laboratory-order' vs 'http://fhir.ch/ig/ch-lab-report/StructureDefinition/ch-lab-report-servicerequest' |
| 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](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](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](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.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).' |
| Name | Value | Comments | |
|---|---|---|---|
| abstract | false | ||
| baseDefinition | http://fhir.ch/ig/ch-lab-report/StructureDefinition/ch-lab-servicerequest-laboratory-order | http://fhir.ch/ig/ch-lab-report/StructureDefinition/ch-lab-report-servicerequest |
|
| copyright | CC0-1.0 | ||
| date | 2023-09-13T14:45:41+02:00 | 2024-01-31T12:55:13+01:00 |
|
| description | This CH ELM base profile constrains the ServiceRequest resource for the purpose of laboratory orders. | ||
| experimental | |||
| fhirVersion | 4.0.1 | ||
| jurisdiction | |||
| jurisdiction[0] | urn:iso:std:iso:3166#CHE | ||
| kind | resource | ||
| name | ChElmServiceRequestLaboratoryOrder | ||
| publisher | Federal Office of Public Health FOPH | ||
| purpose | |||
| status | draft | active |
|
| title | CH ELM ServiceRequest: Laboratory Order | ||
| type | ServiceRequest | ||
| url | http://fhir.ch/ig/ch-elm/StructureDefinition/ch-elm-servicerequest-laboratory-order | ||
| version | 1.0.0-trialuse | 1.1.0 |
|
| Name | L Flags | L Card. | L Type | L Description & Constraints | R Flags | R Card. | L Type | L Description & Constraints | Comments | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
 ServiceRequest | C | 0..* | CH ELM ServiceRequest: Laboratory Order | C | 0..* | ChLabReportServiceRequest | CH ELM ServiceRequest: Laboratory Order | ||||||||||
 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 | Σ | 1..1 | Identifier | Identifiers assigned to this order | Σ | 1..1 | Identifier | Identifiers assigned to this order | |||||||||
 id | 0..1 | string | Unique id for inter-element referencing |
| |||||||||||||
| Slices for extension | 0..* | Extension | Additional content defined by implementations Slice: Unordered, Open by value:url |
| |||||||||||||
| use | ?!Σ | 0..1 | code | usual | official | temp | secondary | old (If known) Binding: ?? (required): Identifies the purpose for this identifier, if known . |
| ||||||||||||
| type | Σ | 0..1 | CodeableConcept | Description of identifier Binding: ?? (extensible): A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. |
| ||||||||||||
| system | Σ | 1..1 | uri | The namespace for the identifier value Example General: http://www.acme.com/identifiers/patient |
| ||||||||||||
| value | Σ | 1..1 | string | The value that is unique Example General: 123456 Max Length: 100 |
| ||||||||||||
| period | Σ | 0..1 | Period | Time period when id is/was valid for use |
| ||||||||||||
| assigner | Σ | 0..1 | Reference(Organization) | Organization that issued id (may be just text) |
| ||||||||||||
| 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. Required Pattern: completed | ?!Σ | 1..1 | code | draft | active | on-hold | revoked | completed | entered-in-error | unknown Binding: ?? (required): The status of a service order. Required Pattern: completed | |||||||||
| intent | ?!Σ | 1..1 | code | proposal | plan | directive | order | original-order | reflex-order | filler-order | instance-order | option Binding: ?? (required): The kind of service request. Required Pattern: order | ?!Σ | 1..1 | code | proposal | plan | directive | order | original-order | reflex-order | filler-order | instance-order | option Binding: ?? (required): The kind of service request. Required Pattern: order | |||||||||
| category | Σ | 0..* | CodeableConcept | Classification of service Binding: ?? (example): Classification of the requested service. Required Pattern: {"coding":[{"system":"http://snomed.info/sct","code":"108252007"}]} | Σ | 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 | 1..1 | ?? | Concept - reference to a terminology or just text Binding: ?? (preferred) | 1..1 | ?? | Concept - reference to a terminology or just text 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 ELM Patient) | Individual or Entity the service is ordered for | Σ | 1..1 | Reference(CH ELM Patient) | 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 | Date request signed | |||||||||
| requester | Σ | 1..1 | Reference(CH ELM PractitionerRole: Orderer) | Who/what is requesting service | Σ | 1..1 | Reference(CH ELM PractitionerRole: Orderer) | 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 | ClaimResponse) | Associated insurance coverage | |||||||||||
| supportingInfo | 0..* | Reference(Resource) | Additional clinical information | 0..* | Reference(Resource) | Additional clinical information | |||||||||||
| specimen | Σ | 1..1 | Reference(CH ELM Specimen: Laboratory) | Procedure Samples | Σ | 1..1 | Reference(CH ELM Specimen: Laboratory) | 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 | |||||||||||||||||