Workflow

HL7 Norway proposed base profiles for Workflow resources in HL7 FHIR R4.

Appointment and ApppointmentResponse profiles and extensions

Only attributes with actual profiling is included in the information model diagram as well as any optional extensions provided as a part of the no-basis package. The model should be forward compatible to Appointment in R5 as far as possible.

Short notice on relationship between no-basis Appointment and no-basis-Encounter

Appointment and Encounter have dependencies as they both describe different aspects of the administrative relationship between patient and health care organizations.

Appointment og AppointmentResponse profiler

Appointment (no:timeavtale; npr:planlagt episode) – describes a planned meeting between a patient and healthcare personell.

Encounter (no: kontakt, besøk, opphold, innleggelse, omsorgsepisode, poliklinisk konsultasjon etc) is defined as: “An interaction between a patient and healthcare provider(s) for the purpose of providing healthcare service(s) or assessing the health status of a patient”. An inpatient encounter (no:inneliggende) is an encounter that can consist of several sub-encounters – for example a radiology examination or a surgery. The national base profile have defined an extension in no-basis-Appointment to mirror this partOf-pattern in the encounter.

The normal scenario is that the Appointment resource is used until the patient is registered as arrived. After arrival the Encounter resource is used to share information about the interaction. Due to the fact that the Encounter resource contains more clinical related information than Appointment, some EHRs may use Encounter with status planned to share information about the interaction also before the patient is registered as arrived.

Inspection (no: tilsyn) are normally not registered as independent encounters in the EHR, but represents and interaction between patient and healthcare personell that is documented in an inspection note (no: tilsynsnotat). Local routines as each hospital can choose to register inspections as encounters, but in most cases such a practice will require too much manual registration in the EHR. An inspection can also be registered as a procedure.

EpisodeOfCare (no: henvisningsperiode) can encompass several ambulatory and inpatient encounters across several organizations. The challenge with tracing such patient trajectory (no: pasientforløp) is that the episode of care will encompass several service requests (no: henvisninger) and there are no common identifier that can be used to trace the patient trajectory across these encounters. Helsedirektoratet has earlier pointed to the need for such an identifier (forløpsidentifikator).

no-basis-AppointmentResponse

Base profile for Norwegian AppointmentResponse information. Defined by HL7 Norway. Should be used as a basis for further profiling in use-cases where specific appointment response information is needed. The basis profile is open, but derived profiles should close down the information elements according to specification relevant to the use-case.

The full documentation of the profile no-basis-AppointmentResponse

Resource content

idΣ0..1id
metaΣ0..1Meta
implicitRulesΣ ?!0..1uri
language0..1codeBinding
text0..1Narrative
contained0..*Resource
id0..1string
extensionI0..0Extension
url1..1uriFixed Value
valueBooleanboolean
modifierExtension?! I0..*Extension
identifierΣ0..*Identifier
appointmentΣ1..1Reference(Appointment)
start0..1instant
end0..1instant
participantTypeΣ0..*CodeableConceptBinding
actorΣ0..1Reference(Patient | Practitioner | PractitionerRole | RelatedPerson | Device | HealthcareService | Location)
participantStatusΣ ?!1..1codeBinding
comment0..1string

no-basis-AppointmentResponse

Base profile for Norwegian AppointmentResponse information. Defined by HL7 Norway. Should be used as a basis for further profiling in use-cases where specific appointment response information is needed. The basis profile is open, but derived profiles should close down the information elements according to specification relevant to the use-case.

The full documentation of the profile no-basis-Appointment

Resource content

idΣ0..1id
metaΣ0..1Meta
implicitRulesΣ ?!0..1uri
language0..1codeBinding
text0..1Narrative
contained0..*Resource
virtualServiceS I0..*Extension(Complex)
groupS I0..1Extension(boolean)
partOfS I0..1Extension(Reference(no-basis-Appointment))
modifierExtension?! I0..*Extension
identifierΣ0..*Identifier
statusΣ ?!1..1codeBinding
cancelationReasonΣ0..1CodeableConcept
serviceCategoryΣ0..*CodeableConcept
serviceTypeΣ0..*CodeableConcept
specialtyΣ0..*CodeableConceptBinding
id0..1string
extensionI0..*Extension
omsorgsNivaΣ0..1CodingBinding
kontaktTypeΣ0..1CodingBinding
innbyggerΣ0..1CodingBinding
textΣ0..1string
reasonCodeΣ0..*CodeableConceptBinding
reasonReference0..*Reference(Condition | Procedure | Observation | ImmunizationRecommendation)
priority0..1unsignedInt
description0..1string
supportingInformation0..*Reference(Resource)
startΣ0..1instant
endΣ0..1instant
minutesDuration0..1positiveInt
slot0..*Reference(Slot)
created0..1dateTime
comment0..1string
patientInstruction0..1string
basedOn0..*Reference(ServiceRequest)
id0..1string
extensionI0..*Extension
modifierExtensionΣ ?! I0..*Extension
typeΣ0..*CodeableConceptBinding
actorΣ0..1Reference(Patient | Practitioner | PractitionerRole | RelatedPerson | Device | HealthcareService | Location)
requiredΣ0..1codeBinding
statusΣ1..1codeBinding
period0..1Period
requestedPeriod0..*Period