GP2GP Error Code handling in supplier systems Page 1 of 15
1 Table of Contents 1 Table of Contents... 2 2 Introduction... 3 3 INPS Vision... 3 3.1.1 Error code: 12: Duplicate EHR Extract received... 4 3.1.2 Error Code: 11: failed to successfully integrate EHR Extract... 5 3.1.3 Error Code: 09 EHR Extract received without corresponding request... 6 3.1.4 Error Code: 06 Patient not at surgery... 8 3.1.5 Error Code: 07 GP2GP Messaging is not enabled on this system... 8 3.1.6 Error Code: 08 The System s Configuration prevents it from processing this 9 4 EMIS WEB... 11 5 SystemOne TPP... 13 Page 2 of 15
2 Introduction This document gives you information on how your chosen GP software system handles GP2GP errors, the reasons that these errors occur and what action you should take in these given instances. There are different stages that an error can occur during GP2GP transfer process. Please refer to the below information for further details relating to individual systems. 3 INPS Vision Please refer to the table below for error codes in Vision and any action required by the end user. Code Error message Description Action 06 Patient not at surgery. This should be used when the patient Contact INPS helpdesk identified by the NHS Number in the EHR Request, cannot be located in the local index on the receiving system 07 GP2GP messaging is not enabled on this system. This should be used when a GP2GP message is received whilst the system is configured in the Disabled Mode. Contact INPS helpdesk 08 The system's configuration prevents it from processing this 09 EHR extract received without corresponding request. 10 Failed to successfully generate EHR Extract 11 Failed to successfully integrate EHR Extract. This should be used when a GP2GP Message is received whilst the Safe Exchange Framework is enabled and the received message breaks the processing rules. This should be used when a GP2GP message is received by a system that has not previously sent an EHR Request message This should be used when a system fails to generate the EHR Extract for sending This should be used when a system fails to successfully integrate the received EHR Extract into the clinical system Contact INPS helpdesk Contact INPS helpdesk Contact INPS helpdesk 12 Duplicate EHR Extract This should be used when a system Contact INPS helpdesk None Page 3 of 15
received. receives a subsequent copy of an EHR extract after it has previously integrated one for the current registration 99 Unexpected condition. This is a code that should only be used in circumstances where the above codes cannot be used to accurately describe the condition Contact INPS helpdesk 3.1.1 Error code: 12: Duplicate EHR Extract received When the old practice sends an EHR Extract more than once, in such cases the extract gets rejected from the new practice, stating the code. New Practice: Old Practice: Page 4 of 15
3.1.2 Error Code: 11: failed to successfully integrate EHR Extract When the new practice fails to integrate the extract it appears in Mail manager as below New Practice: Page 5 of 15
Old Practice: 3.1.3 Error Code: 09 EHR Extract received without corresponding request When the old practice sends an EHR Extract to a practice which doesn t have the corresponding GP2GP request, the extract gets rejected Response from new (requesting) practice Page 6 of 15
Record transfer in the old (sending) practice Page 7 of 15
3.1.4 Error Code: 06 Patient not at surgery When a new practice registers a patient and triggers a GP2GP request, when that patient (NHS Number) is not found at the old practice, the old practice generates and sends an error code. Below is the screen shot from the new practice, where the GP2GP request will be rejected, stating that the patient is not at surgery. 3.1.5 Error Code: 07 GP2GP Messaging is not enabled on this system Page 8 of 15
When a new practice sends a GP2GP request to the old practice, where it is not enabled for GP2GP (this means the site is switched off, but the end point is configured). The GP2GP request will be rejected, stating the reason. Below is the screen shot from the new practice Mail manager. New (requesting) practice 3.1.6 Error Code: 08 The System s Configuration prevents it from processing this Page 9 of 15
This should be used when Safe Exchange Framework is enabled. But Safe Exchange Framework is off, so this error code is N/A. But below screen shot is taken from test systems backup from 2007. Page 10 of 15
4 EMIS WEB Please refer to the table below for error codes in EMIS WEB and any action required by the end user. Code Error message Description Action 06 Patient not recognised at Request rejected because the patient Contact EMIS Support surgery. was not found at the previous practice. 07 GP2GP messaging is not Request rejected because the previous Contact HSCIC Support enabled on this system. practice was not enabled for GP2GP. 08/ The system's configuration Message rejected because of the Safe Contact HSCIC Support SEF001 prevents it from processing this Exchange (SEF) quarantine. 99 Unexpected condition. Message rejected because of a Contact HSCIC Support problem at the previous practice. 07 GP2GP Messaging is not enabled on this system. EHR extract rejected because the new practice is not enabled for GP2GP. Contact HSCIC Support 08/ SEF001 The system's configuration prevents it from processing this 09 EHR extract received without corresponding request. Message rejected because of the Safe Exchange (SEF) quarantine. The new practice rejected the inbound EHR extract message because it was not matched to an EHR request that it had sent. Contact HSCIC Support Contact EMIS Support 11 Failed to successfully integrate EHR Extract. The new practice had a problem integrating the EHR extract OR the new practice rejected the EHR extract. None 12 Duplicate EHR Extract received. The new practice has received the EHR extract more than once. 99 Unexpected condition. Message rejected because of a problem at the New Practice. whilst processing the occurred processing an inbound Inbound Acknowledgment acknowledgment whilst transforming the Inbound Acknowledgement whilst processing the Inbound Record Extract whilst processing the Outbound Extract Acknowledgment occurred transforming an inbound acknowledgment occurred processing an inbound EHR extract occurred processing an outbound acknowledgment message for an EHR extract. Contact EMIS Support Contact EMIS Support Contact EMIS Support Page 11 of 15
99 A problem has occurred whilst sending the Extract Acknowledgement There was an unexpected software problem which prevented the sending of an EHR extract acknowledgement. whilst transforming the Extract whilst Filing the Inbound Message. whilst processing the Inbound Request whilst transforming the Inbound Request whilst processing the Outbound Acknowledgment whilst processing the Outbound Acknowledgment whilst transforming the Outbound Acknowledgement occurred transforming an inbound EHR extract occurred whilst filing an inbound EHR extract into the database. occurred processing an inbound EHR request occurred transforming an inbound request occurred processing an outbound acknowledgement There was an unexpected software problem which prevented the sending of an acknowledgement occurred transforming an outbound acknowledgement Page 12 of 15
5 SystemOne TPP Please refer to the table below for error codes in TPP and any action required by the end user. Error Response Text Guidance on Use Used by Instructions to Users Code 06 Patient not at surgery This should be used when the patient, identified by the NHS Number in the EHR Request, cannot be located in the local index of the receiving system. 07 GP2GP Messaging is not enabled on this system. 09 EHR Extract received without corresponding request. Failed to 10 successfully generate EHR Extract. 11 Failed to successfully integrate EHR Extract. 12 Duplicate EHR Extract received. This should be used when a GP2GP EHR Extract message is received by a system that has not previously sent an EHR Request This should be used when a system fails to generate the EHR Extract for sending. This should be used when a system receives a subsequent copy of an EHR Extract after it has previously integrated one for the current registration. 13 The system s configuration prevents it from processing this 18 Request message not well-formed or not able to be processed Used in GP2GP testing Spine No Action This shall be used in circumstances where the contacted EHR Sender cannot read the received EHR request. It is either corrupt, badly formed or using an incompatible message version. Page 13 of 15
19 Sender check indicates that is not the patient s current healthcare provider 20 Spine system responded with an error 21 EHR Extract message not wellformed or not able to be processed 23 Message not sent because sending practice is not Large Message compliant 24 SDS lookup provided zero or more than one result to the query for each interaction. 26 A-B-A EHR Extract Received and filed as an attachment This shall be used where an EHR Request is received, but checks on PDS indicate that the Requesting practice is not the current primary healthcare provider This shall be used in circumstances where a Spine subsystem such as PDS responds with an error. This should only be used where there isn t a more specific code. This shall be used in circumstances where the EHR cannot process the received EHR It is corrupt, badly formed or using an incompatible message version. This shall be used when the sending practice identifies that the EHR Extract message is a Large Message and the sending practice is NOT large message compliant. Examples of a Large Message: Message too large (>5MB) Too many attachments (>100 inc HL7) Unsupported file type attachment This should be used if any SDS lookup fails to return a result or returns more than one result for each interaction in a particular MIM. E.g. 2 results for RCMR_IN030000UK06 (Large Messaging ) No Action No Action. No Action Page 14 of 15
27 Non A-B-A EHR Extract Received and rejected due to data format 28 Non A-B-A EHR Extract Received and rejected due to non-data related reasons 99 Unexpected condition. This should be used when an EHR extract is received in a Non A-B-A scenario, and not integrated into the EHR because the data structure was inconsistent with the current system and the user preferred to wait for the paper record and re-enter. This should be used when an EHR extract is received in a Non A-B-A scenario, and not integrated into the EHR for non-data related reasons. This is a code that should only be used in circumstances where the above codes cannot be used to accurately describe the condition. No Action No Action Page 15 of 15