ITB Implementation Guide, published by . This guide is not an authorized publication; it is the continuous build for version 0.1.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/espen-servicewell/wof-portal-fhir-ig/ 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.
The following artifacts define the specific capabilities that different types of systems are expected to have in order to comply with this implementation guide. Systems conforming to this implementation guide are expected to declare conformance to one or more of the following capability statements.
ITB capability statement |
This is the FHIR capability statement for the ITB interface |
These define constraints on FHIR resources for systems conforming to this implementation guide.
ITB ActivityDefinition |
ITBActivityDefinition is used to handle .. |
ITB Appointment |
ITBAppointment is used to handle .. |
ITB AppointmentResponse |
ITBAppointmentResponse is used to handle .. |
ITB Endpoint |
ITB Endpoint is used to handle .. |
ITB HealthcareService |
ITBHealthcareService… |
ITB List |
ITBList is used to hold PriceDefinitions… |
ITB Location |
ITBLocation is used to handle adress and position, for example used in ITBHealthCareService |
ITB Organization |
TBD |
ITB Patient | |
ITB Practitioner |
Practitioner is.. TBD |
ITB PractitionerRole |
PractitionerRole is an actor in Patient Portal and can become a bookable entity |
ITB Schedule | |
ITB Slot | |
Portal Clinical Organization |
This resource can be used to handle clinical organizations |
Portal Person |
This resource can be used to handle for example related persons, patients and practitioners |
These define constraints on FHIR data types for systems conforming to this implementation guide.
WofMeta |
Special MetaProfile for Wof to hold meta data about the resource (internal use only) |
These define constraints on FHIR data types for systems conforming to this implementation guide.
AllowReschedulingFromDentalUnitLocation | |
AllowedActions | |
Attachment Extension |
Extension used to be able add attachments to a resource |
Consent to marketing Extension |
Used to handle consent to marketing |
Created | |
ExtEndpointStatusMessage | |
ITB Binary Reference Extension |
Extension used to be able to inlude binaries in the resource |
ITB List Reference Extension |
Extension used to be able to add lists |
ITB Price Definition Extension |
Extension used to be able to define prices |
ITB Source System User Id Extension |
Extension used to handle Source System User Id |
ITB Url Placeholder Extension |
Used in URL's for linking to this instance. Should be short and url-friendly |
Name as code Extension |
Extension used to handle code for name |
NotBookableInITB | |
Opus Booking Category Extension |
Sets the BookingCategory in OpusDental. Maps to ValuSet vsOpusBookingCategory |
OpusCryptobookingText Extension |
Special cryptated text for OpusDental Booking description. Maps to ValueSet |
PlanningHorizonInWeeks | |
Portal Created Extension |
Used in meta to specify date create |
PractitionerSegmentsPlusDefaultsTo | |
RowVersion | |
Tenant Identifier Extension |
Extension used to be able to inlude binaries in the resource |
TimeToPersist |
Parameter to make it possible to clean unwanted resources when TimeToPersist is passed |
UsePractitionerSegments | |
UsePractitionerSegments | |
WofMeta | |
bookingInformation | |
externalBookingUrl | |
hasExternalBookingSite |
These define sets of codes used by systems conforming to this implementation guide.
AllowedActionsVS |
Valid values for wofmeta-allowed actions |
ITB Role Codes |
This value set defines role codes |
ITB Service Types |
This value set defines service types |
ITB Speciality Codes |
This value set defines speciality code |
Opus Identifiers |
This value set defines Opus identifiers |
These define new code systems used by systems conforming to this implementation guide.
ITB Booking Categories |
ITB Booking Categories |
ITB Practitioner Role Codes |
ITB Practitioner Role Codes |
ITB Service Types |
ITB Service Types |
Opus Identifiers |
Opus Identifiers |
These are example instances that show what data produced and consumed by systems conforming with this implementation guide might look like.