ChildPatientUniversal Tabular View
COCD_TP145230GB02 | |||||||||||||||||||||||||||||||||
PatientRole |
This template class constrains the CDA PatientRole class. The purpose of this template is to allow child patient information that would normally be retrieved from the Personal Demographics Service (PDS) to be carried in a CDA document. This is to allow sending and receiving systems which do not have access to PDS to be able to identify the child patient using a wider range of information than just NHS number. This template does not support the full child patient information obtainable from PDS only the information that is supported by CDA. This subset of child patient information is sufficient for use in CDA document exchanges. This template also constrains the child patient information supported by CDA to make it suitable for NHS use. |
||||||||||||||||||||||||||||||||
Used by: | |||||||||||||||||||||||||||||||||
[1..1] [M] classCode (CS { CNE: RoleClass } ) { Fixed="PAT" } |
Model Attribute Description The HL7 attribute classCode uses a code to describe this class as a role of patient. Implementation in XML Instance
|
||||||||||||||||||||||||||||||||
[0..4] addr (SET<AD>) |
Model Attribute Description The HL7 attribute addr uses a set of addresses for the patient (this is limited to a maximum of 4 types to reduce display issues in rendering CDA documents). The HL7 attribute addr allows structured and unstructured addresses to be carried. Only structured addresses are recommended to be used. Implementation in XML Instance There are a number of forms of structured address. The three shown here are the recommended formats for patient addresses, they are listed in no particular order. The XML element addr is populated as follows: When using the structured address in the style of PDS the XML element addr shall contain five XML elements streetAddressLine:
The first XML element streetAddressLine or the second XML element streetAddressLine and the fourth XML element streetAddressLine are mandatory to be populated.
When using the fully structured address format then the XML element addr shall be populated as follows:
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 XML element addr also allows an XML attribute use and this should be used to further define the patient address type when required. Only the use values listed below are recommended to be used for patient addresses.
When the XML attribute use of the XML element addr contains the value "PHYS" then the following two XML elements of the XML element addr may be populated.
The XML element useablePeriod of XML element addr can be used to indicate some of the following types of valid times for an address:
|
||||||||||||||||||||||||||||||||
[1..2] [M] id (SET<II>) |
Model Attribute Description The HL7 attribute id enables the identification of the patient using the NHS number, or a local identifier if the NHS number is not available. This attribute has been extended for NHS use to allow the status of the NHS number to also be stated. Implementation in XML Instance There must be either one or two instances of id.
For a verified NHS Number:
For an unverified NHS Number:
When the NHS Number is not included then:
A local identifier for the patient may also be included in the second instance of id as below:
|
||||||||||||||||||||||||||||||||
[1..1] [M] templateId (II) { Fixed="COCD_TP145230GB02#PatientRole" } |
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.
|
||||||||||||||||||||||||||||||||
[1..1] [M] patientPatient (Patient) |
A link to the patient class. |
||||||||||||||||||||||||||||||||
[0..1] providerOrganization (Organization) |
A link to the organisation class that provides the care. |
||||||||||||||||||||||||||||||||
Patient |
This template class constrains the CDA Patient class. This class details information about the person who is the patient. |
||||||||||||||||||||||||||||||||
Used by: PatientRole | |||||||||||||||||||||||||||||||||
[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
|
||||||||||||||||||||||||||||||||
[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
|
||||||||||||||||||||||||||||||||
[1..1] [M] administrativeGenderCode (CV { CNE:Sex } ) |
Model Attribute Description The HL7 attribute administrativeGenderCode uses a code from the Sex vocabulary to indicate the gender of the patient. This code is for administrative purposes only and does not imply a particular genetic or physical sex. Implementation in XML Instance The Coded Plain data type flavour of Coded Value (CV) shall be used to carry this information in the XML element administrativeGenderCode as follows:
|
||||||||||||||||||||||||||||||||
[1..1] [M] birthTime (TS) |
Model Attribute Description The HL7 attribute birthTime specifies the patient's date of birth. Implementation in XML Instance The XML attribute value of the XML element birthTime shall be populated a time stamp in the format yyyymmddhhmm where:
At least the year must be present. The XML attribute value of the XML element birthTime should be populated to the level of detail that is available on the sending system. |
||||||||||||||||||||||||||||||||
[1..4] [R] name (SET<PN>) |
Model Attribute Description The HL7 attribute name provides names associated with the person who is the patient. 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 patient's name. This information is carried in the XML element name as follows:
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 *
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 patient, some uses are shown below:
When no patient name is available to the sending system to then an appropriate XML attribute nullFlavor may be used to populate the XML element name. The recommended values for the XML attribute nullFlavor are listed below:
|
||||||||||||||||||||||||||||||||
[1..1] [M] templateId (II) { Fixed="COCD_TP145230GB02#patientPatient" } |
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 InstanceThe Identifier External data type flavour is used to carry this information in the XML element templateId as follows:
|
||||||||||||||||||||||||||||||||
[0..*] guardian (Guardian) |
A link to the guardian.
|
||||||||||||||||||||||||||||||||
Guardian |
This template class constrains the CDA Guardian class. This class is used to carry information about the person or organisation who/which is or acts as the patient's guardian. |
||||||||||||||||||||||||||||||||
Used by: Patient | |||||||||||||||||||||||||||||||||
[1..1] [M] classCode (CS { CNE: RoleClass } ) { Fixed="GUARD" } |
Model Attribute Description The HL7 attribute classCode describes this class as a guardian role. Implementation in XML Instance
|
||||||||||||||||||||||||||||||||
[0..4] addr (SET<AD>) |
Model Attribute Description The HL7 attribute addr uses a set of addresses for the patient's guardian (this is limited to a maximum of 4 types to reduce display issues in rendering CDA documents). The HL7 attribute addr allows structured and unstructured addresses to be carried. Only structured addresses are recommended to be used. Implementation in XML Instance There are a number of forms of structured address. The three shown here are the recommended formats for patient addresses, they are listed in no particular order. The XML element addr is populated as follows: When using the structured address in the style of PDS the XML element addr shall contain five XML elements streetAddressLine:
The first XML element streetAddressLine or the second XML element streetAddressLine and the fourth XML element streetAddressLine are mandatory to be populated.
When using the fully structured address format then the XML element addr shall be populated as follows:
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 XML element addr also allows an XML attribute use and this should be used to further define the patient address type when required. Only the use values listed below are recommended to be used for patient addresses.
When the XML attribute use of the XML element addr contains the value "PHYS" then the following two XML elements of the XML element addr may be populated.
The XML element useablePeriod of XML element addr can be used to indicate some of the following types of valid times for an address:
|
||||||||||||||||||||||||||||||||
[1..1] [R] code (CV { CNE:GuardianRoleType } ) |
Model Attribute Description 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:
When no code is available then this attribute show be nulled using a null flavor as below:
When the guardian is not a person then this attribute show be nulled using a null flavor as below:
|
||||||||||||||||||||||||||||||||
[1..2] [M] id (SET<II>) |
Model Attribute Description The HL7 attribute id enables the identification of the guardian using the NHS number, or a local identifier if the NHS number is not available. This attribute has been extended for NHS use to allow the status of the NHS number to also be stated. Implementation in XML Instance There must be either one or two instances of id.
For a verified NHS Number:
For an unverified NHS Number:
When the NHS Number is not included then:
A local identifier for the patient may also be included in the second instance of id as below:
|
||||||||||||||||||||||||||||||||
[0..4] telecom (SET<TEL>) |
Model Attribute Description The HL7 Attribute telecom specifies contact details for the guardian in the form of telephone numbers, fax numbers and email addresses. Implementation in XML Instance The XML value attribute of the XML element telecom should contain the telephone / fax number or an email address prefixed by the type of contact and a colon.
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 to be used for the patient contact details:
The XML element useablePeriod of the 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 for office hours (9am to 5 pm). It can be used to indicate some of the following types of valid times:
|
||||||||||||||||||||||||||||||||
[1..1] [M] templateId (II) { Fixed="COCD_TP145230GB02#guardian" } |
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:
|
||||||||||||||||||||||||||||||||
[1..1] [M] guardianGuardianChoice (GuardianChoice) |
A link to the choice of guardian.
|
||||||||||||||||||||||||||||||||
GuardianChoice |
The choice of a person or organisation guardian.
|
||||||||||||||||||||||||||||||||
Used by: Guardian | |||||||||||||||||||||||||||||||||
[1..1] either: GuardianOrganization |
The guardian organisation.
|
||||||||||||||||||||||||||||||||
... or ... : GuardianPerson |
The guardian person.
|
||||||||||||||||||||||||||||||||
GuardianOrganization |
This template class constrains the CDA Organization class. This class contains the details of the organisation which is acting as the patient's guardian. |
||||||||||||||||||||||||||||||||
Used by: Guardian,GuardianChoice | |||||||||||||||||||||||||||||||||
[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
|
||||||||||||||||||||||||||||||||
[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
|
||||||||||||||||||||||||||||||||
[0..1] addr (AD) |
Model Attribute Description The HL7 attribute addr provides a contact address for the organisation. 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 or second XML element streetAddressLine and the fourth XML element streetAddressLine are mandated to be populated.
or the address may use the fully structured address:
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 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.
The XML element useablePeriod of XML element addr can be used to indicate some of the following types of valid times:
|
||||||||||||||||||||||||||||||||
[1..1] [M] id (II) |
Model Attribute Description The HL7 attribute id uses an ODS code as an identifier that uniquely identifies the organisation which is acting as the patient's guardian. 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:
When ODS organisation code is used then the XML element id is populated in the following way:
|
||||||||||||||||||||||||||||||||
[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] standardIndustryClassCode (CV { CNE:GuardianOrganisationType } ) |
Model Attribute Description The HL7 attribute standardIndustryClassCode uses a code taken from the GuardianOrganisationType vocabulary to indicate the type of care provider. The only use currently for this attribute is to indicate that the organisation is the patient's registered GP practice. Implementation in XML Instance
|
||||||||||||||||||||||||||||||||
[0..4] telecom (SET<TEL>) |
Model Attribute Description
The HL7 attribute telecom provides contact details for the organisation 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.
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 an organisation's contact details:
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 for office hours (9am to 5 pm). It can be used to indicate some of the following types of valid times:
|
||||||||||||||||||||||||||||||||
[1..1] [M] templateId (II) { Fixed="COCD_TP145230GB02#guardianOrganization" } |
Model Attribute Description
The HL7 attribute templateId provides a unique identifier for the template and the classname 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:
|
||||||||||||||||||||||||||||||||
GuardianPerson |
This template class constrains the CDA Person class. This class contains the details of the person who is the patient's guardian. |
||||||||||||||||||||||||||||||||
Used by: Guardian,GuardianChoice | |||||||||||||||||||||||||||||||||
[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
|
||||||||||||||||||||||||||||||||
[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
|
||||||||||||||||||||||||||||||||
[1..*] [R] name (SET<PN>) |
Model Attribute Description The HL7 attribute name provides a name associated with the person who is the patient's guardian. 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 guardian's name. This information is carried in the XML element name as follows:
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 *
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 guardian, some uses are shown below:
|
||||||||||||||||||||||||||||||||
[1..1] [M] templateId (II) { Fixed="COCD_TP145230GB02#guardianPerson" } |
Model Attribute Description
The HL7 attribute templateId provides a unique identifier for the template and the classname 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:
|
||||||||||||||||||||||||||||||||
Organization |
This template class constrains the CDA Organization class. This class details the organisation which provides/provided care to the patient. |
||||||||||||||||||||||||||||||||
Used by: OrganisationPartOf,PatientRole | |||||||||||||||||||||||||||||||||
[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
|
||||||||||||||||||||||||||||||||
[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
|
||||||||||||||||||||||||||||||||
[0..1] addr (AD) |
Model Attribute Description The HL7 attribute addr provides a contact address for the organisation. 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 or second XML element streetAddressLine and the fourth XML element streetAddressLine are mandated to be populated.
or the address may use the fully structured address:
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 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.
The XML element useablePeriod of XML element addr can be used to indicate some of the following types of valid times:
|
||||||||||||||||||||||||||||||||
[1..1] [M] id (II) |
Model Attribute Description The HL7 attribute id uses an ODS code as an identifier that uniquely identifies the organisation which provides/provided care to the patient. 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:
When ODS organisation code is used then the XML element id is populated in the following way:
|
||||||||||||||||||||||||||||||||
[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] standardIndustryClassCode (CV { CNE:CDAOrganizationProviderType } ) |
Model Attribute Description The HL7 attribute standardIndustryClassCode uses a code taken from the CDAOrganizationProviderType vocabulary to indicate the type of care provider. The only use currently for this attribute is to indicate that the organisation is the patient's registered GP practice. Implementation in XML Instance
|
||||||||||||||||||||||||||||||||
[0..4] telecom (SET<TEL>) |
Model Attribute Description The HL7 attribute telecom provides contact details for the organisation 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.
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 an organisation's contact details:
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 for office hours (9am to 5 pm). It can be used to indicate some of the following types of valid times:
|
||||||||||||||||||||||||||||||||
[1..1] [M] templateId (II) { Fixed="COCD_TP145230GB02#providerOrganization" } |
Model Attribute Description Implementation in XML Instance The Identifier External data type flavour is used to carry this information in the XML element templateId as follows:
|
||||||||||||||||||||||||||||||||
[0..*] playedOrganisationPartOf (OrganisationPartOf) |
A link to the organization.
|
||||||||||||||||||||||||||||||||
OrganisationPartOf |
This template class constrains the CDA OrganisationPartOf class. This class is used to carry information about the organisation the provider organisation is part of. |
||||||||||||||||||||||||||||||||
Used by: Organization | |||||||||||||||||||||||||||||||||
[1..1] [M] classCode (CS { CNE: RoleClass } ) { Fixed="PART" } |
Model Attribute Description The HL7 attribute classCode describes this class as a part role. Implementation in XML Instance
|
||||||||||||||||||||||||||||||||
[1..2] [R] id (SET) |
Model Attribute Description The HL7 attribute id uses an ODS code as an identifier that uniquely identifies the organisation which provides/provided care to the patient. 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:
When ODS organisation code is used then the XML element id is populated in the following way:
When no identifier is available then this attribute show be nulled using a null flavor as below:
|
||||||||||||||||||||||||||||||||
[1..1] [M] templateId (II) { Fixed="COCD_TP145230GB02#playedOrganisationPartOf" } |
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:
|
||||||||||||||||||||||||||||||||
[0..1] wholeOrganization (Organization) |
A link to the organization part of.
|