Structured Headings
Domain Message Specification

Version: 1.0; Status: RC3

RecipientNonClinicalPerson Tabular View

COCD_TP145242GB01
IntendedRecipient

This template class constrains the CDA IntendedRecipient class.

A template for information about a non clinical person recipient, required to be sent between systems.
Used by:
[1..1] [M] classCode (CS { CNE: RoleClass } )
{ Fixed="ASSIGNED" }

Model Attribute Description

The HL7 attribute classCode describes this class as an assigned role. An assigned role is a type of agent in which, the player is a person that might represent a scoping organisation.

Implementation in XML Instance

  • The XML attribute classCode is fixed to "ASSIGNED".
[0..1] addr (AD)

Model Attribute Description

The HL7 attribute addr provides an address associated with the role.

This address is used to identify the address associated with the recipient; for example the GP practice address of the patient's GP.

The HL7 attribute addr allows structured and unstructured addresses to be carried in an instance. Only structured addresses are recommended to be used. There are a number of structured forms of addresses. The three shown here are the recommended formats for organisation addresses, they are listed in no particular order.

Implementation in XML Instance

When the structured address in the style of PDS is used then it shall contain five XML elements streetAddressLine.

  • The first XML element streetAddressLine should contain the premises name
  • The second XML element streetAddressLine should contain the number and thoroughfare
  • The third XML element streetAddressLine should contain the locality
  • The fourth XML element streetAddressLine should contain the post town
  • The fifth XML element streetAddressLine should contain the county

The first XML element streetAddressLine or second XML element streetAddressLine and the fourth XML element streetAddressLine are mandated to be populated.

  • The XML element postalCode may be used to carry a postcode
  • The XML element addressKey may be used to carry a PAF key

or the address may use the fully structured address:

  • The XML element houseNumber should contain the house/building number or name
  • The XML element streetName should contain contains the street name
  • The XML element city should contain the city name
  • The XML element county should contain the county
  • The XML element country should contain the country name
  • The XML element postalCode should contain the post code
  • The XML element addressKey should contain the address key

Alternatively the structured address may contain just a series of XML elements streetAddressLine populated in the correct order to render as a postal address with as much information as available included.

  • The first XML element streetAddressLine contains the first address line
  • The second XML element streetAddressLine contains the second address line
  • The third XML element streetAddressLine contains the third address line
  • and so on ....

The XML element addr allows an XML attribute use, this should be used to further define the organisation address when required. Only the use values listed below are recommended to be used for organisation addresses.

Code
Definition
WP Work place - An office address. First choice for business related contacts during business hours.
TMP Temporary address - May be good for visit or mailing.
PHYS Physical visit address - Used primarily to visit an address.
PST
 Postal address - Used to send mail.

The XML element useablePeriod of XML element addr can be used to indicate some of the following types of valid times:

  • A point in time when the contact address details are valid
  • A start and end time
    • Just including hours and minutes to indicate opening hours
    • Using dates for indicating a contact address is only for a certain period of time
  • A start time only to indicate when the contact address is valid from
  • An end time only to indicate that the contact address is only valid until a certain date
[1..1] [R] id (II)

Model Attribute Description

The HL7 attribute id allows for the role to be identified using local identifiers. This may be done when there is a local requirement, when no local requirement exists the id should be nulled.

Implementation in XML Instance

Where there is a local requirement for the role to be identified using a local identifier and an OID is available on the sending system then:

  • The XML attribute root shall contain the OID for the identifying system.
  • The XML attribute extension shall contain the recipient's identifier.

Where there is a local requirement for the role to be identified using a local identifier and no OID is available on the sending system then:

  • The XML attribute root shall contain the OID "2.16.840.1.113883.2.1.3.2.4.18.24".
  • The XML attribute extension shall contain the recipient's role identifier.
  • The XML attribute assigningAuthorityName shall contain the assigning organisation in the format of ODSCode:ODSName, for example:
assigningAuthorityName="RA9:SOUTH DEVON HEALTHCARE NHS TRUST"

When no local requirement exists the XML attribute nullFlavor of the XML element id should contain "NA".

[1..1] [M] recipientRoleCode (CV { CWE:RecipientNonClinicalPersonType } )
Model Attribute Description

The HL7 attribute recipientRoleCode uses a code from the RecipientNonClinicalPersonType vocabulary to describe the role of the non clinical person who is the recipient.

Implementation in XML Instance

The Coded Plain flavour of the Coded Value (CV) data type shall be used to carry this information in the XML element code as follows:

  • The XML attribute code shall contain a code from the RecipientNonClinicalPersonType vocabulary
  • The XML attribute codeSystem shall contain the OID "2.16.840.1.113883.2.1.3.2.4.17.510"
  • The XML attribute displayName shall carry the description for the code from the RecipientNonClinicalPersonType vocabulary.
[0..*] telecom (SET<TEL>)

Model Attribute Description

The HL7 attribute telecom provides contact details for the person playing the role in the form of telephone numbers, fax numbers and email addresses.

Implementation in XML Instance

This XML element telecom should be populated as below:

The XML attribute value of the XML element telecom should contain the telephone / fax number or an email address prefixed by the type of contact and a colon.

  • For a telephone number the actual telephone number would be prefixed with tel:
  • For a fax number the actual fax number would be prefixed with fax:
  • For an email address the actual email address would be prefixed with mailto:

The XML attribute use of the XML element telecom may be used to give further information about the type of contact details contained in the XML attribute value. Only the use values listed below are recommended for the contact details associated with the role:

Code Definition
AS Answering service - an automated answering machine used for less urgent cases and if the main purpose of contact is to leave a message or access an automated announcement.
EC
Emergency contact - A contact specifically designated to be used for emergencies. This is the first choice in emergencies, independent of any other use codes.

The XML element useablePeriod of XML element telecom may be used to indicate when the contact details given are valid, for example to indicate that a telephone number is only or office hours (9am to 5 pm). It can be used to indicate some of the following types of valid times:

  • A point in time when the contact details are valid
  • A start and end time
    • Just including hours and minutes to indicate opening hours
    • Using dates for indicating a contact is only for a certain period of time
  • A start time only to indicate when the contact details are valid from
  • An end time only to indicate that the contact details are only valid until a certain date
[1..1] [M] templateId (II)
{ Fixed="COCD_TP145242GB01#IntendedRecipient" }
Model Attribute Description

The HL7 attribute templateId provides a unique identifier for the template and the class name within that template. This is used to identify how the CDA standard has been constrained for NHS use.

Implementation in XML Instance

The Identifier External data type flavour is used to carry this information in the XML element templateId as follows:
  • The XML attribute root is fixed to the OID "2.16.840.1.113883.2.1.3.2.4.18.2"
  • The XML attribute extension is fixed to "COCD_TP145242GB01#IntendedRecipient"
[1..1] [M] assignedPerson (Person)
A link to the person playing this role.
[0..1] representedOrganization (Organization)
A link to the scoping organisation.
Person

This template class constrains the CDA Person class.

A class which details the person who is the recipient.
Used by: IntendedRecipient
[1..1] [M] classCode (CS { CNE: EntityClass } )
{ Fixed="PSN" }

Model Attribute Description

The HL7 attribute classCode describes this class as a person.

Implementation in XML Instance

  • The XML attribute classCode is fixed to "PSN".
[1..1] [M] determinerCode (CS { CNE: EntityDeterminer } )
{ Fixed="INSTANCE" }

Model Attribute Description

The HL7 attribute determinerCode describes this class as an instance of a person.

Implementation in XML Instance

  • The XML attribute determinerCode is fixed to "INSTANCE".
[1..1] [M] name (PN)

Model Attribute Description

The HL7 attribute name provides a name associated with the person who is the recipient.

Implementation in XML Instance

The Person Name Structured with optional Use and optional Valid Time flavour of the PN data type is the recommended format for the recipient's name. This information is carried in the XML element name as follows:

  • The XML element prefix should contain the recipient's title
  • The XML element given should contain the recipient's forenames; there can be as many occurrences of the XML element as required
  • The XML element family should contain the recipient's surname
  • The XML element suffix may contain any suffix for the recipient

Additionally the XML attribute use of the XML element name should be used to indicate the type of name; the recommended codes to be used are listed below:

Note some of the codes listed are NHS extensions, these are marked with an *

Code Definition
L
 Legal
PREFERRED *
 Preferred name

Additionally the XML element validTime of the XML element name may be used to indicate the time when the name is valid/was valid for the recipient, some uses are shown below:

  • A point in time when the name details are known to be valid
  • A start and end time
    • To represent the period of time the recipient is/was known by this name
  • A start time only to indicate when the name is/was valid from for the recipient
  • An end time only to indicate that the name is/was only valid for the recipient until a certain date

[1..1] [M] templateId (II)
{ Fixed="COCD_TP145242GB01#assignedPerson" }
Model Attribute Description

The HL7 attribute templateId provides a unique identifier for the template and the class name within that template. This is used to identify how the CDA standard has been constrained for NHS use.

Implementation in XML Instance

The Identifier External data type flavour is used to carry this information in the XML element templateId as follows:
  • The XML attribute root is fixed to the OID "2.16.840.1.113883.2.1.3.2.4.18.2"
  • The XML attribute extension is fixed to "COCD_TP145242GB01#assignedPerson"
Organization

This template class constrains the CDA Organization class.

This optional class details the organisation which scopes the role of the recipient (the recipient person may either be registered to, or may be employed by this organisation).
Used by: IntendedRecipient
[1..1] [M] classCode (CS { CNE: EntityClass } )
{ Fixed="ORG" }

Model Attribute Description

The HL7 attribute classCode describes this class as an organisation.

Implementation in XML Instance

  • The XML attribute classCode is fixed to "ORG".
[1..1] [M] determinerCode (CS { CNE: EntityDeterminer } )
{ Fixed="INSTANCE" }

Model Attribute Description

The HL7 attribute determinerCode describes this class as an instance of an organisation.

Implementation in XML Instance

  • The XML attribute determinerCode is fixed to "INSTANCE".
[0..1] id (II)

Model Attribute Description

The HL7 attribute id uses an ODS code as an identifier that uniquely identifies the organisation which the recipient is registered with. The ODS code should identify the organisation at either the site level or organisation level. Where possible the organisation should be identified at the site level. ODS codes were formerly known as NACS codes.

Implementation in XML Instance

When ODS site code is used then the XML element id is populated in the following way:

  • The XML attribute root shall contain an OID with the value "2.16.840.1.113883.2.1.3.2.4.19.2"
  • The XML attribute extension shall contain the ODS site code.

When ODS organisation code is used then the XML element id is populated in the following way:

  • The XML attribute root shall contain an OID with the value "2.16.840.1.113883.2.1.3.2.4.19.1"
  • The XML attribute extension shall contain the ODS organisation code.
[1..1] [M] name (ON)

Model Attribute Description

The HL7 attribute name uses the description of the organisation associated with the ODS code.

Implementation in XML Instance

  • The XML element name will carry the description associated with the ODS code carried in the XML attribute extension of the XML element id.
[1..1] [M] templateId (II)
{ Fixed="COCD_TP145242GB01#representedOrganization" }

Model Attribute Description

The HL7 attribute templateId provides a unique identifier for the template and the class name within that template. This is used to identify how the CDA standard has been constrained for NHS use.

Implementation in XML Instance

The Identifier External data type flavour is used to carry this information in the XML element templateId as follows:

  • The XML attribute root is fixed to the OID "2.16.840.1.113883.2.1.3.2.4.18.2"
  • The XML attribute extension is fixed to "COCD_TP145242GB01#representedOrganization".