This portal provides an open platform for user feedback and product change requests. Anyone can add an idea and remain as a Guest, but please consider signing up so that others can see who has created the ideas!
Note: this is a public facing web portal, any text here can be viewed by anyone over the internet, so please consider carefully the content you wish to share and please do not post anything of a sensitive nature.
Chintan asked me to post this idea on this idea forum rather than the exchange portal.
We have hit an issue relating to automation of the entire process for pushing patient data.
E.g. If I push data into the local fhir appliance and it's successful, I get a 201/200 status code.
But - behind the scenes the fhir appliance communicates with the PIX and does its work. If there is an issue with a patient and the PIX returns an error code, e.g. : "DEMOG-9999 - Generic Spine Service Errors" or "SMSP-0000 - Success, error type: verification, verification errors: Requested given name initial does not match PDS" - then this information is never communicated back to the integration server.
We do not have the resources to monitor the PIX failures via the console, it also increases risk as it adds a human element that is prone to error, forgetfulness, annual leave, sickness etc.
The process of monitoring and notification of success/failure at both the local and regional level needs to be automated.
The only current way we can reliably use is to tail the logs and look for “ERROR” before trying to parse them. This is prone to any future changes that may be introduced into log creation etc so is not sustainable.
I’m not sure if the errors are saved into the fhir appliance database?
I propose some new api endpoints on the fhir appliance that I can call periodically:
The ability to get all errors - within date/time parameters or last xx period
Get all errors related to a specific error[s] code[s] (with date/time or period etc)
Get all errors relater to a specific NHS/local reference/PIX reference (with date/time or period etc)
If the above apis are available we can then move to a “manage by exception” method, reduce both staff workloads and patient risk.
| As a | System integrator |
| I would like | New API endpoints on the local fhir appliance |
| So that | Automate the integration process with a failsafe feedback method that works 24/7 |
| User contact | adam.jennison@hullcc.gov.uk |
|
Other information
We have hit an issue relating to automation of the entire process for pushing patient data. E.g. If I push data into the local fhir appliance and it's successful, I get a 201/200 status code. But - behind the scenes the fhir appliance communicates with the PIX and does its work. If there is an issue with a patient and the PIX returns an error code, e.g. : "DEMOG-9999 - Generic Spine Service Errors" or "SMSP-0000 - Success, error type: verification, verification errors: Requested given name initial does not match PDS" - then this information is never communicated back to the integration server. We do not have the resources to monitor the PIX failures via the console, it also increases risk as it adds a human element that is prone to error, forgetfulness, annual leave, sickness etc. The process of monitoring and notification of success/failure at both the local and regional level needs to be automated.
The only current way we can reliably use is to tail the logs and look for “ERROR” before trying to parse them. This is prone to any future changes that may be introduced into log creation etc so is not sustainable. I’m not sure if the errors are saved into the fhir appliance database? I propose some new api endpoints on the fhir appliance that I can call periodically: |
|
Is this an idea you still want to progress with Adam? Judging by the previous comments, it looks like you have what you need.
PSA - in case anyone else requires this info:
I was informed that this functionality is included in the local FHIR appliance via
/fhir/stu3/Patient?_tag=https://yhcr.nhs.uk/pix/registration/status|failed
and
/fhir/stu3/Patient?_tag=https://yhcr.nhs.uk/pix/registration/status|error
The error codes provided by the PIX are embedded within a text field rather than a json attribute.
Can this ticket be changed so the PIX error codes are available as an attribute, this will allow automated routing.
The returned dataset is paged, there is info in the json data as the page number etc - the call for the next page is called via this endpoint:
fhir/stu3/Patient?_queryId=<guid>&_page=<page number>
Chintan asked me to post this idea on this idea forum rather than the exchange portal.
We have hit an issue relating to automation of the entire process for pushing patient data.
E.g. If I push data into the local fhir appliance and it's successful, I get a 201/200 status code.
But - behind the scenes the fhir appliance communicates with the PIX and does its work. If there is an issue with a patient and the PIX returns an error code, e.g. : "DEMOG-9999 - Generic Spine Service Errors" or "SMSP-0000 - Success, error type: verification, verification errors: Requested given name initial does not match PDS" - then this information is never communicated back to the integration server.
We do not have the staff availability to work through the console and monitor the PIX failures via the console, it also increases risk as it adds a human element that is prone to error, forgetfulness, annual leave, sickness etc.
The process of monitoring and notification (on errors) needs to be automated.
The only current way is to tail the logs and look for “ERROR” before trying to parse them.
I’m not sure if the errors are saved into the fhir appliance database?
I propose some new api endpoints on the fhir appliance that I can call periodically:
The ability to get all errors - within date/time parameters or last xx period
Get all errors related to a specific error[s] code[s]
Get all errors relater to a specific NHS/local reference/PIX reference
If the above apis are available we can then move to a “manage by exception” method.