Search loading...

API Hub

Explore and Make use of Nationally Defined Messaging APIs

 

Attendance Details Section

Gives information about the Attendance details section

Attendance Details Section content

The Attendance details section carries information about the patient’s attendance at the Outpatient department. PRSB Elements should be formatted as subheadings in any HTML sent:

Section Description Card. MRO* FHIR Target and Guidance
Attendance details The details of the patient contact. 1 only M Carried in the CodeableConcept of Composition.section.code FHIR element.
PRSB Element Description Card. MRO* FHIR Target and Guidance
Date and time of contact Date and time of the appointment, contact or attendance. 1 only M The date and time of appointment as recorded on the Patient Administration System (PAS) as text and carried in the Encounter.period.start and Encounter.period.end FHIR element.
Contact type First contact, follow-up contact. 0 to 1 O Text. Contact type may come from those recorded on the local PAS.NHS Data dictionary First attendance.
  • 1   First attendance face to face
  • 2   Follow-up attendance face to face
  • 3   First telephone or telemedicine consultation
  • 4   Follow-up telephone or telemedicine consultation
This should also be carried in the FHIR element Encounter.type and as this is an example ValueSet the Encounter.type.Coding.system should contain the value "https://www.datadictionary.nhs.uk".
Consultation method CONSULTATION METHOD USED identifies the communication mechanism used to relay information between the CARE PROFESSIONAL and the PERSON who is the subject of the consultation, during the Outpatient encounter 0 to 1 R Text only, but may be derived from Consultation method from NHS Data Dictionary.
  • Face-to-face,
  • telephone,
  • tele medicine web camera,
  • talk type for a PERSON unable to speak
Responsible healthcare professional The name and designation of the consultant, nurse consultant, midwife, allied health professional who has overall responsibility for the patient (may not actually see the patient) 1 only M The name and identifier of the consultant from a recognised source such as the Spine Directory Service, or a local identifier. Any identifiers MUST NOT be carried as text. The following FHIR Elements SHOULD be populated in the Practitioner and PractitionerRole Resources:
  • Encounter.participant.individual.
    Reference.Practitioner.identifier
  • Encounter.participant.individual.
    Reference.Practitioner.name
  • PractitionerRole.code
  • PractitionerRole.identifier
Specialty Specialties designated by royal colleges and faculties. E.g. orthopaedics, renal medicine, endocrinology, etc 0 to 1 R Text for either the main specialty of the responsible clinician (as held on the Spine Directory Service), or the department from which the patient is attending. The specialty SHOULD be populated in the PractitionerRole.specialty FHIR element. The profile is currently bound to the FHIR ValueSet c80-practice-codes as preferred. This is proposed to be replaced by NHS Data main specialty code and therefore the current guidance is to not use the preferred ValueSet but to replace it using a code from MAIN SPECIALTY CODE. The FHIR CodeSystem element should be populated with "https://www.datadictionary.nhs.uk". As an alternative this element may be populated with a SNOMED CT concept and the FHIR CodeSystem element populated with "http://snomed.info/sct". Note further guidance will be issues in a later release of the specification.
Service Treatment functions or services. E.g. hand surgery, back surgery, hand clinic, TIA clinic, falls clinic, speech and language therapy, dialysis, family therapy, pre-admission assessment clinic, etc 0 to 1 R Text only.
Seen by Doctor, nurse or other healthcare professional that sees the patient. Record the most senior member of staff present. Includes name, role, telephone number 1 to many M The name and identifier of the consultant from a recognised source such as the Spine Directory Service, or a local identifier. Any identifiers MUST NOT be carried as text. The following FHIR Elements SHOULD be populated in the Practitioner and PractitionerRole Resources:
  • Encounter.participant.individual.
    Reference.Practitioner.identifier
  • Encounter.participant.individual.
    Reference.Practitioner.name
  • PractitionerRole.code
  • PractitionerRole.identifier
Care professionals present The name, designation of the additional individuals or team members including consultant(s), nurse consultant(s), allied health professional(s), social worker(s) 0 to many O The name and identifier of the consultant from a recognised source such as the Spine Directory Service, or a local identifier. Any identifiers MUST NOT be carried as text. The following FHIR Elements SHOULD be populated in the Practitioner and PractitionerRole Resources:
  • Encounter.participant.individual.
    Reference.Practitioner.identifier
  • Encounter.participant.individual.
    Reference.Practitioner.name
  • PractitionerRole.code
  • PractitionerRole.identifier
Person accompanying patient Identify, where clinically relevant, others accompanying the patient, e.g. relative, friend, informal carer, advocate. If the patient was not present, was an authorised representative present? Includes: Name, Relationship, Role (patient advocate) 0 to 1 O Information provided by patient or person accompanying patient.Text and where possible the name and identifier of the consultant from a recognised source such as the Spine Directory Service, or a local identifier. Any identifiers MUST NOT be carried as text. The following FHIR Elements SHOULD be populated in the Practitioner and PractitionerRole Resources:
  • Encounter.participant.individual.
    Reference.Practitioner.identifier
  • Encounter.participant.individual.
    Reference.Practitioner.name
  • PractitionerRole.code
  • PractitionerRole.identifier
Outcome of outpatient attendance This records the outcome of an Out-Patient Attendance 0 to 1 R Text and carried in the FHIR extension CareConnect-OutcomeOfAttendance-1 of the ITK3 Encounter Profile CareConnect-ITK-Encounter-1.
* M=Mandatory R=Required O=Optional

Example Attendance Details Section

Coded Resources

This text section should be linked to the following FHIR Resources to provide the textual information in a coded format.

  • The ITK3 FHIR Outpatient Letter does not currently support coded Attendance details.
Tags: fhir

All content is available under the Open Government Licence v3.0, except where otherwise stated