1 Overview
- 1.1 When Creating a New Patient
  - 1.1.1 Relevant Entities
  - 1.1.2 Definition
  - 1.1.3 Examples
  - 1.1.4 Response

Overview

This message will either create or update a medical record in PKB. If the specified medical record (identified by the PID segment) is not found, it will be created. Otherwise, it will be updated.

If an update is performed, then the entire set of medications, allergies or diagnoses sent by your Organisation will be replaced, depending on what is sent. Note - this includes any medications, allergies or diagnoses added by a Professional from your Organisation. For example, if a Professional from your Organisation manually adds an allergy, but then a different allergy is provided in an A28 message from your Organisation, the entry manually added by the Professional will be replaced.

If you provide an email address in the message then this will be added to the record and the patient will be sent an email invitation to register (unless they have already registered, in which case they are sent a request to confirm the newly added email address). You are able to provide an email address in both PID-13 and PID-14, but a maximum of 1 from each field can be accepted. See here for more information on how PKB handles email addresses.

When Creating a New Patient

The following fields need be included in your HL7 message:

at least 1 identifier (either National ID, Organisation Level ID, or Team Level ID)
first name
last name
Date of Birth
Gender (sex at birth)

Relevant Entities

Patient demographic information is used to populate [[Patient]] entities, including [[Contact]], [[National ID]], [[Organisation Level ID]] and [[Team Level ID]] entities. [[National ID Type]], [[Organisation Level ID Type]] and [[Team Level ID Type]] must match pre-agreed information; new types cannot be created via HL7 messaging.
Allergy information is used to populate [[Allergy]] entities
Diagnosis information is used to populate [[Diagnosis]] entities
Medication information is used to populate [[Medication]] entities

Please click through to the Data Model to explore the presentation of these entities in the web interface.

[[Patient]]

Matched on: See our notes on identifiers & matching for full details of our approach to matching [[Patient]] entities via HL7.

When matched: Partial update will be performed on the [[Patient]] if the supplied MSH-7 timestamp is greater than or equal to [[Patient.Entered Timestamp]] held on the record. Note: the [[Patient.Entered Timestamp]] may have been set via any route e.g HL7, FHIR or UI. See our PID specification for which fields will be left unmodified if a blank is provided.

When not matched: New [[Patient]] created. [[Patient.Entered Timestamp]] will be set to the value in MSH-7.

[[Contact]]

Matched on: [[Contact.Type]] and [[Contact.Value]]. Note that only email contacts can be added via HL7 - the phone number is stored directly on the [[Patient]].

When matched: No action. Any contacts already known will remain on the record.

When not matched: New [[Contact]] created. If this is the first email address for the record then an invitation to register will be sent to the email address. If there was already an email address on the record then a confirmation request will be sent to the email address. See our notes on email address handling for more information.

[[National ID]]

Matched on: Since only a single National ID for any given National ID Type is permitted on a medical record, an instance of a National ID for a patient can be matched on the [[National ID Type]] alone.

When matched: The corresponding [[National ID.Value]] is updated if a valid value was provided. An existing National ID can be changed but not removed.

When not matched: New [[National ID]] added to the medical record.

[[National ID Type]]

Matched on: [[National ID Type.HL7 Assigning Authority]] as derived from PID-2.4 and PID-3.4 and [[National ID Type.HL7 Type Code]] as derived from PID-2.5 and PID-3.5.

When matched: Matching the type is a prerequisite for processing the corresponding National ID.

When not matched: The corresponding National ID is silently ignored. New types cannot be created via HL7 messaging.

[[Organisation Level ID]]

Matched on: [[Organisation Level ID.Value]] as derived from PID-2.1 and PID-3.1 in conjunction with the specified [[Organisation Level ID Type]]

When matched: No action. Any Organisation Level IDs already known will remain on the record.

When not matched: New [[Organisation Level ID]] added to the medical record.

[[Organisation Level ID Type]]

Matched on: [[Organisation Level ID Type.HL7 Assigning Authority]] as derived from PID-2.4 and PID-3.4 and [[Organisation Level ID Type.HL7 Type Code]] as derived from PID-2.5 and PID-3.5.

When matched: Matching the type is a prerequisite for processing the corresponding Organisation Level ID.

When not matched: The corresponding Organisation Level ID is silently ignored. New types cannot be created via HL7 messaging.

[[Team Level ID]]

Matched on: [[Team Level ID.Value]] as derived from PID-2.1 and PID-3.1 in conjunction with the specified [[Team Level ID Type]]

When matched: No action. Any Team Level IDs already known will remain on the record.

When not matched: New [[Team Level ID]] added to the medical record.

[[Team Level ID Type]]

Matched on: [[Team Level ID Type.HL7 Assigning Authority]] as derived from PID-2.4 and PID-3.4 and [[Team Level ID Type.HL7 Type Code]] as derived from PID-2.5 and PID-3.5.

When matched: Matching the type is a prerequisite for processing the corresponding Team Level ID.

When not matched: The corresponding Team Level ID is silently ignored. New types cannot be created via HL7 messaging.

[[Allergy]]

Matched on: [[Allergy.Allergen]] as derived from AL1-3 and [[Allergen.Onset Timestamp]] as derived from AL1-6.

When matched: The matching [[Allergy]] is replaced with the new information. A partial update is not performed. Note: Any allergies previously stored by this organisation, but which were not provided this time, will be deleted.

When not matched: A new [[Allergy]] is added to the medical record.

[[Diagnosis]]

Matched on: [[Diagnosis.Diagnosis]] as derived from DG1-3 and [[Diagnosis.Start Date]] as derived from DG1-5.

When matched: The matching [[Diagnosis]] is replaced with the new information. A partial update is not performed. Note: Any diagnoses previously stored by this organisation, but which were not provided this time, will be deleted.

When not matched: A new [[Diagnosis]] is added to the medical record.

[[Medication]]

Matched on: [[Medication.Substance]] as derived from ZRX-2, [[Medication.Start Timestamp]] as derived from ZRX-1.4 and [[Medication.End Timestamp]] as derived from ZRX-1.5.

When matched: The matching [[Medication]] is replaced with the new information. A partial update is not performed. Note: Any medications previously stored by this organisation, but which were not provided this time, will be deleted.

When not matched: A new [[Medication]] is added to the medical record.

Definition

Segment	Field	Opt	RP/#	Component	Description	Example	Data Model

Segment	Field	Opt	RP/#	Component	Description	Example	Data Model
MSH					Message header. This conforms to PKB's standard definition.
PID					Patient identification. This conforms to PKB's standard definition.
{ [ AL1					Allergy information. When creating or updating a medical record you can specify allergy information for the patient. The AL1 segment has no fields to indicate source; to include the provider who entered the allergy, use a NTE segment following it. When updating - the specified information replaces any existing allergy information from the sender. Duplicate allergies within the AL1 set will result in the entire message being rejected. An allergy is identified as being duplicate if AL1-3 (allergen) and AL1-6 (identification date) match that of another AL1 segment within the message. The duplicate check within AL1-3 (allergen) gives precedence to the uniqueness of either AL1-3.1 (code) or AL1-3.5 (alternate coding). When coding values are not supplied in AL1-3 then the check references AL1-3.2 (text) or AL1-3.5 (alternate text) instead. The duplicate check is conducted versus the other AL1 segments in the message.
	AL1-3	R			Allergen. Read V2 codes can be mapped to privacy labels if sent in AL1-3. See the coded data page for more information. Although each component is optional individually, at least one of AL1-3.1 or AL1-3.2 must be provided.		[[Allergy.Allergen]]
				AL1-3.1	Allergen code	A_01
				AL1-3.2	Allergen text	Paracetamol
				AL1-3.3	Allergen coding system
				AL1-3.4	Allergen alternate code	A.1
				AL1-3.5	Allergen alternate text	Paracetamol
				AL1-3.6	Allergen alternate coding system	INT
	AL1-4	O			Allergen severity		[[Allergy.Severity]]
				AL1-4.1	Allergen severity code	S_01
				AL1-4.2	Allergen severity text	Mild
				AL1-4.3	Allergen severity coding system	HOSP
				AL1-4.4	Allergen severity alternate code	RS.M
				AL1-4.5	Allergen severity alternate text	Mild
				AL1-4.6	Allergen severity alternate coding system
	AL1-5	O	Y		Allergy reaction
				AL1-5.1	Allergy reaction code	Coughing, Sneezing	[[Allergy.Reactions]]
	AL1-6	O			Identification date
				AL1-6.1	Identification date	201408310408	[[Allergy.Onset Timestamp]]
[ NTE ] ] }					An NTE can be optionally included after an AL1 to specify source information.
	NTE-5	O			Source information. If provided, at least the family name must be given.		[[Allergy->Source.Source Text]]
				NTE-5.2	Family name	Foster
				NTE-5.3	Given name	John
				NTE-5.4	Middle names	Harry
				NTE-5.6	Prefix	Dr
{ [ DG1 ] }					Diagnosis information. When creating or updating a medical record you can specify diagnosis information for the patient. When updating - the specified information replaces any existing diagnosis information from the sender. Duplicate diagnosis within the DG1 set will result in the entire message being rejected. A diagnosis is identified as being duplicate if DG1-3 (diagnosis) and DG1-5 (diagnosis timestamp) match that of another DG1 segment within the message. The duplicate check within DG1-3 (diagnosis) gives precedence to the uniqueness of either DG1-3.1 (code) or DG1-3.5 (alternate coding). When coding values are not supplied in DG1-3 then the check references DG1-3.2 (text) or DG1-3.5 (alternate text) instead. The duplicate check is conducted versus the other DG1 segments in the message.
	DG1-3	R			Diagnosis. Read V2 codes can be mapped to privacy labels if sent in DG1-3. See the coded data page for more information. Although each component is optional individually, at least one of DG1-3.1 or DG1-3.2 must be provided.		[[Diagnosis.Diagnosis]]
				DG1-3.1	Diagnosis code	D01
				DG1-3.2	Diagnosis text	Asthma
				DG1-3.3	Diagnosis coding system	HOSP
				DG1-3.4	Diagnosis alternate code	D.100
				DG1-3.5	Diagnosis alternate text	Asthma
				DG1-3.6	Diagnosis alternate coding system
	DG1-5	O			Diagnosis timestamp

ADT A28 - Create A New Record

Overview

When Creating a New Patient

Relevant Entities

Definition