Healthcare Service Registry

Extension - Management Cluster

Canonical URL:https://nshealth.ca/fhir/StructureDefinition/Extension-ManagementCluster

Formal Views of Profile Content

Description of Profiles, Differentials, Snapshots and how the different presentations work

ExtensionManagementCluster (Extension)	I		Extension	There are no (further) constraints on this element Element id Extension Short description Optional Extensions Element Definition Optional Extension Element - found in all resources. Data type Extension Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ext-1: Must have either extensions or value[x], not both `extension.exists() != value.exists()` Mappings rim: n/a rim: N/A
id		0..1	string	There are no (further) constraints on this element Element id Extension.id Short description Unique id for inter-element referencing Definition Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Data type string Mappings rim: n/a
extension	I	0..*	Extension	There are no (further) constraints on this element Element id Extension.extension Short description Additional content defined by implementations Alternate names extensions, user content Definition May be used to represent additional information that is not part of the basic definition of the element. 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. Comments There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ext-1: Must have either extensions or value[x], not both `extension.exists() != value.exists()` Mappings rim: n/a rim: N/A
url		1..1	uriFixed Value	Element id Extension.url Short description identifies the meaning of the extension Definition Source of the definition for the extension code - a logical name or a URL. Comments The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. Data type uri Fixed value https://nshealth.ca/fhir/StructureDefinition/Extension-ManagementCluster Mappings rim: N/A
value[x]		1..1	Binding	Element id Extension.value[x] Short description Value of extension Definition Value of extension - must be one of a constrained set of the data types (see Extensibility for a list). Binding NSHAManagementCluster (required) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a rim: N/A
valueCoding			Coding	Data type Coding

Usage

The Appointment resource is used to represent a meeting planned in response to a ServiceRequest. References to other resources are used to convey the details of the appointment including ServiceRequest the appointment is based on (Appointment.basedOn) and participants (Appointment.participant.actor) in the appointment such as a Patient, PractitionerRole or HealthcareService.

Notes

.id

used to uniquely identify the resource
if a persistent identity for the resource is not available to use when constructing a message Bundle for transmission via Direct Messaging, a UUID SHOULD be used in this element (with a corresponding value in Bundle.entry.fullUrl)

.meta.profile

used to declare conformance to this profile
populate with a fixed value: http://ehealthontario.ca/fhir/StructureDefinition/ca-on-eReferral-profile-Appointment|1.0.0

.text

used to provide human readable human readable that can be pasted into other systems with complete information about the appointment
where populated:
- .text.div SHALL include a full text summary of the appointment
- .text.status, populate with the fixed code "generated"

.status

typically populated with "booked" (or "cancelled" if unbooked)

.appointmentType

typically populated with "INTAKE" or "ASSESSMENT" for a referral appointment

.description

title of the appointment (e.g. the Subject on an appointemnt in MS Outlook)

.start

populate with the appointment start time
format: YYYY-MM-DDThh:mm:ss.sss+zz:zz (e.g. 2015-02-07T13:28:17.239+02:00 or 2017-01-01T00:00:00Z).

.end

populate with the appointment end time
format: YYYY-MM-DDThh:mm:ss.sss+zz:zz (e.g. 2015-02-07T13:28:17.239+02:00 or 2017-01-01T00:00:00Z).

.minutesDuration

duration of appointment in minutes
populate with a positive integer

.created

populate with the date that this appointment was initially created (NOT the time of the appointment itself)

.comment

additional comments and details about the appointment (i.e. the Body of an appointment in MS Outlook)

.patientInstruction

detailed information and instructions for the patient

.basedOn

associates the Appointment with the ServiceRequest being performed
SHALL be populated with a reference to the ServiceRequest being performed
if the Appointment is being transmitted via messaging, the referenced ServiceRequest resource SHALL be included in the message as a Bundle.entry

.participant

repeating element identifies one or more participants in the appointment where
- .participant.type is a value from ParticipantType(extensible)
- .participant.actor a reference to one of:
  - the Patient being seen > SHALL be the same as the ServiceRequest.subject
  - the HealthcareService providing the appointment > SHALL be same as the ServiceRequest.performer if both are present
  - the PractitionerRole seeing the patient
  - the Location of the appointment
- .participant.status is expected to be "accepted" for a booked appointemnt
Note:
- if an Appointment is being transmitted via messaging, referenced Patient, PractitionerRole and Location resources SHALL be included in the message as a Bundle.entry
- HealthcareService SHOULD typically be an external reference