Trailblazers and pilots |
Issues Resolution |
|||||||
The accumulated experience from formal (trailblazer and pilot sites) and informal implementations of electronic pathology results reporting over the last 10 years has provided compelling evidence that the NHS Information Authority should take full control of the process and invest resources to ensure strong quality assurance of EDI activities. This was necessary to ensure both clinical efficiency and clinical effectiveness. Several Trust and GP implementations that adopted the existing documented national standards have been evaluated. To date the NHSIA has examined some 24,000 test messages transmitted over 42 months by 50 laboratories using these standards. Formal examinations of implementations using alternative, often tailored, information standards has not been undertaken as such studies would have been difficult and costly. However it is likely that similar findings would be found and that generic solutions apply equally to all EDI implementations. The main findings of the evaluation raised serious questions of concern in relation to both clinical efficiency and effectiveness: Clinical efficiency several examples pointed to efficiency gains which could be made if there were greater harmonisation of the working practices for generation and use of electronic pathology results information between laboratory and GP practice. Clinical effectiveness - the evaluations have exposed some areas of concern as to the reliability and accuracy of some Trust pathology messaging software implementations. Such systems software issues have potential implications for any form of pathology messaging, be it national standard based or locally developed. These, combined with the identification of some dubious working practices at both sending and receiving sites, were identified as posing potential threats to clinical safety. To successfully implement pathology messaging a Trust effectively needs three pieces of software: the pathology computer system, message translation/construction software and NHSnet transmission software. With very few exceptions, current implementations of EDI reporting have purchased each piece of software independently. This has led directly to a failure of many of these systems to interact successfully so that information content has been lost, misinterpreted or amended as it has passed between the various components. Procedures have been recommended for resolving all of the issues and these have been built into the specifications for laboratory report messaging. For example, a pathology-specific bounded list of READ codes has been produced (this is not affected by the terminology collaboration between the NHS and College of American Pathologists to combine SNOMED® RT and READ Codes version 3); recommendations for error-free mapping have been made; and a number of important changes to the pathology report message profile have been made to improve consistency. |
A list of 56 unresolved issues (see Table 1)
were identified from the pilot sites evaluation and published on the PATHEDI website
(www.leeds.ac.uk/acb/pathedi) in 1999 and an Issues Resolution Mechanism (IRM) was set up
to deal with them. An Issues Resolution Forum (IRF) PMEP technical team consisting
of representative pathologists, GPs, pathology and GP system suppliers and NHSIA analysts
reached a consensus agreement about how each issue should be resolved and these were put
out for discussion on the PATHEDI website during mid 2000. Table 1. Some of the issues identified
|
Approach adopted for success
A complete set of specifications for secure pathology report messaging was completed in August 2000. Trusts, software suppliers and technical implementers can now use these to set up electronic reporting of pathology results to GPs to meet the national standards and business requirements. These specifications do not include GP requesting standards.
A separate collaboration between the PMEP and the Encryption Programme Board has produced security requirements which have been built into the specifications. The contract for providing cryptographic security to all transactions was awarded in November 2000 to ENTRUST.
The new Pathology Results Implementation Project (PRIP) will support local implementations to ensure government target dates are met.
A full message checking service is being established to provide immediate support for message development and implementation testing as well as future support for ongoing QA of EDI practice. A recommendation has been made that testing of Trust implementations should fit within the existing laboratory accreditation procedures.
Existing users of commercial laboratory computer systems should now enquire of their supplier when and how their system will be updated to meet the new specifications. Trusts, which are in the process of procuring new or replacement laboratory computer systems, should now ensure the relevant EDI reporting requirements are built into their strategies, specifications, evaluation criteria and contract documentation.
XML versus EDIFACT
Government IT chiefs announced in September 2000 that XML (Extended Markup Language) is to be the standard for developing data integration across the whole public sector. However NHSIA have said that XML is not ready for use in key parts of the health service, particularly pathology messaging. Instead it will rely on 25 year old EDI technology: "At present XML was uncoordinated and EDIFACT remained a more reliable methodology."
This article was published in Biomedical
Gazette October 2000 pp.946/7
Last updated 04 October 2012