CH ORF (R4)
3.0.0-ci-build - ci-build
CH ORF (R4)
3.0.0-ci-build - ci-build
CH ORF (R4), published by HL7 Switzerland. This guide is not an authorized publication; it is the continuous build for version 3.0.0-ci-build built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/hl7ch/ch-orf/ and changes regularly. See the Directory of published versions
Contents:
This page provides a list of the FHIR artifacts defined as part of this implementation guide.
These define forms used by systems conforming to this implementation guide to capture or expose data to end users.
| Module Questionnaire Address |
Subquestionnaire address |
| Module Questionnaire Appointment |
Subquestionnaire appointment |
| Module Questionnaire Consent |
Subquestionnaire consent |
| Module Questionnaire Coverage |
Subquestionnaire coverage |
| Module Questionnaire Familydoctor |
Subquestionnaire familyDoctor |
| Module Questionnaire Initiator |
Subquestionnaire initiator |
| Module Questionnaire Order |
Subquestionnaire order |
| Module Questionnaire Patient |
Subquestionnaire patient |
| Module Questionnaire Practitioner Name Tel |
Subquestionnaire Practitioner with Name and Telecom |
| Module Questionnaire Receiver |
Subquestionnaire receiver |
| Module Questionnaire Receiver Copy |
Subquestionnaire receiverCopy |
| Module Questionnaire Requested Encounter |
Subquestionnaire requestedEncounter |
| Module Questionnaire Sender |
Subquestionnaire sender |
These define constraints on FHIR resources for systems conforming to this implementation guide.
| CH ORF Appointment |
Profile to describe the location and time for the fulfillment of the service request. In this resource, the status of the appointment is defined, patient-oriented instructions are listed here and where and when the service request is to be fulfilled. |
| CH ORF Composition |
Profile to specify how the generic elements (e.g. patient, author) and the healthcare domain specific elements must be structured in the Composition as the first entry of the document. |
| CH ORF Consent |
Profile to specify if the patient gave an informed consent to this order; in particulars for spitex and transfer to retirement home etc. |
| CH ORF Coverage |
Profile to specify how the coverage is represented. This provides an organization or the individual, which will pay for services requested. |
| CH ORF Document |
Profile to set constraints that specify the CH ORF-conformant presentation of a document. The CH ORF exchange format is defined as a document type corresponding to a Bundle resource. |
| CH ORF DocumentReference |
Profile to describe how to provide a reference to a document to make it available to a healthcare system. |
| CH ORF Episode of Care |
Profile to document the antecedent episode of care e.g hospitalisation in case of care transfer between instituitons e.g. hospitals, rehab. clinics, retirement homes etc. |
| CH ORF Location |
Profile to define the details of the location of the appointment. |
| CH ORF Questionnaire |
Profile to define how a CH ORF-conformant Questionnaire resource must be structured. This is independent of the content and content structure of the questionnaire instance itself. |
| CH ORF QuestionnaireResponse |
Profile to define how a CH ORF-conformant QuestionnaireResponse resource must be structured. This is independent of the content and content structure of the response items to a specific questionnaire. |
| CH ORF Requested Encounter |
Profile to describe which details are represented at the requested encounter for the fulfillment of the service request. These are, for example, the status of the encounter or the class and the desired accomodation during the encounter. |
| CH ORF ServiceRequest |
Profile to define how the record of a request for service to be performed is represented in the context of an order. This resource is used to share relevant information required to support an CH ORF request from the order placer to the order filler. |
These define constraints on FHIR data types for systems conforming to this implementation guide.
| CH ORF Consent Code |
Consent Code |
| CH ORF Consent Note |
Consent Note |
| CH ORF Copy Receiver |
Receiver of the copy of this order and the results therefrom |
| CH ORF Desired Accommodation |
Desired Accommodation during the Requested Encounter. |
| CH ORF Episode of Care |
Documentation of the antecedent episode of care e.g hospitalisation in case of care transfer between instituitons e.g. hospitals, rehab. clinics, retirement homes etc. |
| CH ORF Initiator |
Initiator and his realtion to the patient |
| CH ORF Location and Time |
Location and Time of ServiceRequest Fulfillment. |
| CH ORF Patient Consent |
Patient Consent to this Order |
| CH ORF Precedent Document |
Identifier of the document which precedes this document in a thread. |
| CH ORF Receiver |
Person/organization who receives the document |
| CH ORF Requested Encounter Details |
Requested Encounter Details for ServiceRequest Fulfillment. |
| CH ORF Urgent Notification Contact For The Response To This Document |
An information recipient to notify for urgent matters about the response. (e.g. in a clinical setting, the referring doctor has to be called by phone right away at the time the images and reports arrive. The Urgent Notification Contact for the Response can be specified already in the request. At the time the response is written, this element shall be populated to the Urgent Notification Contact element in the response.) |
| CH ORF Urgent Notification Contact For This Documet |
An information recipient to notify for urgent matters (e.g. in a radiology service, the radiologist has to be called by phone right away at the time the doucment is received). |
These define sets of codes used by systems conforming to this implementation guide.
| Appointment Status |
Value Set for CH ORF Appointment Status |
| Consent Status |
Value Set for CH ORF Consent Status |
| Coverage Identifier Type |
Value Set for CH ORF Coverage Identifier Type |
| Coverage Type |
Value Set for CH ORF Coverage Type |
| Desired Accommodation |
Value Set for CH ORF Desired Accomodation |
| Encounter Class |
Value Set for CH ORF Encounter Class |
| Legal Relation |
Value Set for Legal Relation |
| Personal Relation |
Value Set for Personal Relation |
These define new code systems used by systems conforming to this implementation guide.
| Consent Status |
Value Set for CH ORF Consent Status |
| Coverage Identifier Type |
Code System for CH ORF Coverage Identifier Type |
| Coverage Type |
Code System for CH ORF Coverage Type |
These define transformations to convert between data structures used by systems conforming to this implementation guide.
| Map ORF |
Mapping ORF QuestionnaireResponse to Bundle |
These are example instances that show what data produced and consumed by systems conforming with this implementation guide might look like.
| Appointment Booked |
Example for Appointment with status=booked |
| Appointment Pending |
Example for Appointment with status=pending |
| Appointment Proposed |
Example for Appointment with status=proposed |
| Bundle Order-Referral-Form |
Example for Bundle |
| Composition Order-Referral-Form |
Example for Composition |
| Composition Spitex-Order |
Example for Composition |
| Consent |
Example for Consent |
| Copy Receiver Praxis Seeblick |
Example for PractitionerRole |
| Copy Receiver Sabine Meier |
Example for Practitioner |
| Copy Receiver Sabine Meier @ Praxis Seeblick |
Example for PractitionerRole |
| Coverage KVG |
Example for Coverage |
| Coverage Self (Patient) |
Example for Coverage |
| Coverage Self (RelatedPerson) |
Example for Coverage |
| DocumentReference |
Example for DocumentReference |
| Eisode of Care |
Example for Discharge Date in EpisodeOfCare |
| Encounter Emergency |
Example for Encounter |
| Erika Musterfrau |
Example for Patient |
| Florence Amily |
Example for Practitioner |
| Florence Amily @ Praxis Allzeitbereit |
Example for PractitionerRole |
| Hans Röntgen |
Example for Practitioner |
| Hans Röntgen @ Kantonsspital |
Example for PractitionerRole |
| Kantonsspital |
Example for Organization |
| Location of Appointment |
Example for Location |
| Max Ufferer |
Example for Related Person (Husband of Susanna Ufferer) |
| Notification Contact Hans Röntgen |
Example for Practitioner |
| Notification Contact Hans Röntgen |
Example for PractitionerRole |
| Notification Contact Sabine Meier |
Example for Practitioner |
| Notification Contact Sabine Meier |
Example for PractitionerRole |
| Order External Diagnostics |
Example for Bundle |
| Praxis Seeblick |
Example for Organization |
| Questionnaire Order-Referral-Form |
Example for Questionnaire |
| Questionnaire Order-Referral-Form (Modular version) |
Example for Questionnaire (Modular version) |
| QuestionnaireResponse External Diagnostics Order |
Example for QuestionnaireResponse |
| QuestionnaireResponse Medical Referral |
Example for QuestionnaireResponse |
| QuestionnaireResponse Radiology Order |
Example for QuestionnaireResponse |
| Radiology Order |
Example for Bundle |
| SDCModularQuestionnaireExampleForIssue126 |
SDC Modular Questionnaire Example for Issue 126 |
| Sabine Meier |
Example for Practitioner |
| Sabine Meier @ Praxis Seeblick |
Example for PractitionerRole |
| Samuel Pitex |
Example for Practitioner |
| ServiceRequest Order-Referral-Form |
Example for ServiceRequest |
| Spital Trubschachen |
Example for Organization |
| Spitex |
Example for PractitionerRole |
| Stabilo Boss |
Example for Practitioner |
| Stabilo Boss @ Praxis Seeblick |
Example for PractitionerRole |
| Susanna Ufferer |
Example for Patient |
| Thomas Rub |
Example for Practitioner |