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 Attendance details used. 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. 0 to 1 R 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 patient contact or attendance. 1 only M The date and time as recorded by the pharmacy system.
Service The service being provided. 0 to 1 R Coded entry e.g. NUMSAS, private service, Digital Minor Illness Referral Scheme etc.
Organisation name The name, including the identifier, of the organisation where the medicine was supplied. 1 only M This would be generated from the ODS code and associated text.In the future the global location number (GLN) may be used - GS1 standard.
Organisation address The address of the organisation where the medicine was supplied. 0 to 1 R ODS standard but may be generated from the Directory of Services (DOS).
Organisation contact details The contact details of the organisation where the medicine was supplied. For example a phone number, NHSmail address etc. Contact details are used to resolve queries about the record entry. 0 to many R ODS standard but may be generated from the Directory of Services (DOS).
Reason for service The reason why the patient is being supplied the medication as an 'emergency supply of medication' e.g patient is on holiday and has left medication at home. 1 only R This will be free text.
Reason for non-provision of service The reason why the patient was not provided with the service e.g. declined, did not attend etc. 0 TO 1 O Free text e.g. did not attend, declined by patient or clinician etc. Maybe coded text in the future if a reference set is created.
Clinician name The name of the person providing the service, preferably in a structured format. 1 only M The person name as held on the source system. Where possible this should be broken down into its constituent parts (prefix, given name, family name, suffix).
Role The role of the person providing the service. 0 TO 1 R The role may be held on the source system, be from an authoritative source such as SDS, or use an existing vocabulary such as the job role title (from the national workforce dataset).
Professional identifier Professional identifier of the person providing the service. 0 TO 1 R The regulatory body and the identifier itself of the person held on the source system. e.g. GPhC number of the pharmacist.
Person accompanying patient Identify, where clinically relevant, others accompanying the patient, eg parent, relative, friend. Includes: Name, Relationship, role (e.g. informal carer). 0 to many O Free text
Person collecting the medicine The person collecting the emergency supply of medicine (if someone other than the patient). 0 to 1 R Free text
* M=Mandatory R=Required O=Optional

Example Attendance details Section

<xml>
	<section>
		<title value="Attendance Details"/>
		<code>
			<coding>
				<system value="http://snomed.info/sct"/>
				<code value="1077881000000105"/>
				<display value="Attendance details"/>
			</coding>
		</code>
		<text>
		<status value="additional"/>
		<div xmlns="http://www.w3.org/1999/xhtml">
		<table width="100%">
		<tbody>
			<tr>
				<th>Date and time of contact</th>
				<td>9-May-2018 10:00</td>
			</tr>
			<tr>
				<th>Service</th>
				<td>The service being provided.</td>
			</tr>
			<tr>
				<th>Organisation name</th>
				<td>Name: Overtown Pharmacy</td>
			</tr>
			<tr>
				<th>Organisation address</th>
				<td>
					<p>Address:</p>
					<p>Address Line: 1, High Street, Overtown</p>
					<p>City: Leeds</p>
					<p>Post Code: LS1 9AM</p>
				</td>
			</tr>
			<tr>
				<th>Organisation contact details</th>
				<td><p>Contact details: Tel. 01134875516 Email. overtonpharmacy118@mymail.com</td>
			</tr>
			<tr>
				<th>Reason for service</th>
				<td>The reason why the patient is being supplied the medication as an 'emergency supply of medication' e.g patient is on holiday and has left medication at home.</td>
			</tr>
			<tr>
				<th>Reason for non-provision of service</th>
				<td>The reason why the patient was not provided with the service e.g. declined, did not attend etc.</td>
			</tr>
			<tr>
				<th>Clinician name</th>
				<td>The name of the person providing the service, preferably in a structured format.</td>
			</tr>
			<tr>
				<th>Role</th>
				<td>The role of the person providing the service.</td>
			</tr>
			<tr>
				<th>Professional identifier</th>
				<td>Professional identifier of the person providing the service.</td>
			</tr>
			<tr>
				<th>Person accompanying patient</th>
				<td>Identify, where clinically relevant, others accompanying the patient, eg parent, relative, friend. Includes: Name, Relationship, role (e.g. informal carer).</td>
			</tr>
			<tr>
				<th>Person collecting the medicine</th>
				<td>The person collecting the emergency supply of medicine (if someone other than the patient).</td>
			</tr>
		</tbody>
		</table>
	</div>
	</text>
	<!--Reference to Encounter resource as the source of information for this section-->
	<entry>
		<reference value="urn:uuid:adb353f9-0953-4fb4-a4ab-f0ab04a44dbc"/>
	</entry>
</section>
</xml>

Coded Resources

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

  • The Digital Medicines specification does not currently support coded attendance details.
Tags: fhir

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