NPfIT Common Message Element Types Implementation Manual | ||||
Programme |
NPFIT |
DOCUMENT NUMBER | ||
Sub-Prog/Project |
Comms & Messaging |
NPFIT-FNT-TO-DPM-0602 | ||
Prog. Director |
Paul Jones |
|||
Sub-Prog/Proj Mgr |
Ken Lunn | |||
Author |
C&M Development Team |
Version No. |
4.2.00 | |
Contact |
Richard Kavanagh |
Status |
Issued |
Contents
Change History
In Version | Author | Date | Amendment Details |
1.0 | Core Technical Team | 10/5/04 | First Issue |
1.1 | Core Technical Team | 25/6/04 | Updated for new versions of Medication Management CMETs |
1.2 | Core Technical Team | 03/09/04 | Updated to enable wrapper audit requirements and to include new SDS OIDs. |
1.3 | Core Technical Team | 17/09/04 | Added ETP CMETs to support ETP to PPA messaging. Minor modifications to Agent CMET examples. |
1.4 | Core Technical Team | 24/09/04 | Corrected version number for messages, COCT_MT050012UK04 and COCT_MT090120UK04. |
1.5 | Core Technical Team | 29/10/04 | Included new OID and included CMET for GP2GP, RCCT_MT120100UK01. Removal of most of COCT type of CMETs used for Medication Management. Added new versions of UKCT_MT120101 and UKCT_MT120201 for Med. Man. |
1.6 | Core Technical Team | 06/12/04 | Modified hyperlinks for MM CMET's to point to their respective baseline model's tabular view in MM Tabular Views directory. Added paragraph (3) to clarify reasons for artefact name differences between CMET and associated tabular view. |
1.7 | Core Technical Team | 07/01/05 | The artefact identifier for the GP2GP specific R_AgentRole CMET has been reverted back to its original identifier. Included 10 new CMETS (UKCT_MT140101 - UKCT_MT141001) used for POC. |
1.8 | Core Technical Team | 31/03/05 | Removed unused versions of CMETs , New version of POC Clinical statement choice CMET. |
1.9 |
Core Technical Team |
30/06/05 |
Includes MIM-CR-0399, MIM-CR-0436 & MIM-CR-0612 |
1.10 |
C&M Development Team |
30/09/05 |
Changes to support new version of POC messages. Added new version of ETP R_Patient CMET that conforms to PDS patient structure. |
1.11 |
C&M Development Team |
16/12/05 |
Reinstate MIM-CR-0612. Includes MIM-CR-0660 Changes to recommendation CMET and clinical statement choice CMET organizer mood codes. |
1.13 | C&M Development Team | 15/03/06 | Changes to medication CMETS, addition of new CMETS and removal of deprecated CMETs and change to tabular definition in Patient CMET.Minor changes to Clinical statement choice CMET tabular view |
4.1.03 |
C&M development | 07/06/2006 | First Issue |
4.1.04 |
C&M development | 02/08/2006 | Changes to following CMETS
|
4.2.00 |
C&M development | 02/08/2006 |
Added following CMETS (from CMET IM 1.13)
Descriptions in tabular views for CMETs used by GP summary have been further clarified Descriptions in of CMETs in this file have been further clarified |
A CMET (Common Message Element Type) is a message fragment that is available for use in any number of messages across multiple domains. They are used within the NPfIT messages to assist consistent implementation of common components.
This document acts as a central repository for the definition of all CMETs that are used by NPfIT messages. Individual messages that utilise CMETs, provide links to the RMIMs and tabular views in the document.
Identifies or provides detailed information about a person fulfilling an Agent role when it is not known whether all details of one or more of:
are not available from SDS (Spine Directory Services).
This version adds an optional person identifier.
Latest version that supports a scoping organisation.
Identifies a person fulfilling an Agent role, when full details of the person and role and organization are available from SDS (Spine Directory Services).
Identifies or provides detailed information about an organization fulfilling an Agent role when it is not known whether the organization is known to SDS (Spine Directory Services).
Identifies or provides detailed information about an organization fulfilling an Agent role when it is not known whether the organization is known to SDS (Spine Directory Services). This version adds optional location/place information for an organization.
Identifies an organization fulfilling an Agent role, when full details of the organization are available from SDS (Spine Directory Services).
Identifies an organization fulfilling an Agent role, when full details of the organization are available from SDS (Spine Directory Services). This version adds optional location/place information for an organization.
Identifies or provides detailed information about a device fulfilling an Agent role when it is not known whether the device is known to SDS (Spine Directory Services).
Identifies a device fulfilling an Agent role, when full details of the device are available from SDS (Spine Directory Services).
Identifies a specific role, full details of which are available from elsewhere in this message.
ETP Flavour to identify the patient with the supporting details of name, address, etc.
Identifies a specific role, full details of which are available from elsewhere in this message.
Identifies a person fulfilling a specific role. SDS User Id, Role Profile Id and Role Id are mandatory. Full details of the person and role profile are available from SDS.
Identifies a mandatory system which could be software or hardware. Full details of the system are available from SDS.
Identifies an organization fulfilling an Agent role when
The playing organization details maybe or may not be held on SDS
The scoping organization details maybe or may not be not held on SDS
If there is a record of the organization on SDS in either instance then the SDS choice MUST be used.
Identifies a person fulfilling an Agent role when
If there is a record of the role , person or organization on SDS in any instance then the SDS choice MUST be used.
CMET for
Care professional documentation
Third party correspondence
Patient or carer correspondence
Used when any of the above
CMET for observations that relate to
This
This
CMET for recording of care events including but not limited to those which are
Intended
Requested
Promised
Proposed
Booked
CMET for highlighting a clinical statement as a problem.
CMET for link assertion relationships such as but not limited to
CMET to represent a minimal medication record including
CMET to highlight a clinical statement as a risk to persons other than the patient.
CMET to represent diagnoses.
CMET to represent findings such as by not limited to
CMET to represent observations related to family history.
CMET to represent investigative procedures
CMET to represent personal preferences of the patient
CMET to represent services and providers of the service to the patient
CMET to represent an occurrence of a known allergy or adverse reaction event.
CMET to represent advice or information given to a patient or the patient's representive
CMET to represent an administrative procedure.
CMET to represent the presentation text act and its CRE type organizer.
CMET to represent an identified allergy or adverse reaction.
CMET to represent an identified risk to a patient.
CMET to represent treatment given to the patient.
CMET to represent the patients refusal to share information.
For messages that make use of CRE type the mapping of CRE types to CMET and CMET classes is given in this table.
Note this can be tested using this schematron
R_AgentNPFITPerson - UKCT_MT120201UK03
R_AgentNPFITPerson - UKCT_MT120201UK04
R_AgentNPFITOrg - UKCT_MT120401UK02
R_AgentNPFITOrg - UKCT_MT120401UK03
R_AgentNPFITOrgSDS - UKCT_MT120501UK02
R_AgentNPFITIdentified - UKCT_MT120801UK01
R_Patient - COCT_MT050012UK04
R_Patient - COCT_MT050012UK05