|
PSIS Query Implementation Manual |
||||||
Programme |
NPFIT |
DOCUMENT NUMBER |
|||||
Sub-Prog/Project |
Comms & Messaging |
National Prog |
Org |
Prog/Proj |
Doc Type |
Seq |
|
Prog. Director |
Tim Jones |
NPFIT |
FNT |
TO |
DPM |
0097.01 |
|
Sub-Prog/Proj Mgr |
Margaret Baldock |
||||||
Author |
Core Technical Team |
Version No. |
1.5 |
||||
NPO/PSO Contact |
Sarah King |
Status |
Issued |
Contents
Change History
In Version |
Author |
Date |
Amendment Details |
1.0 |
Core Technical Team |
10/05/04 |
First release |
1.1 |
Core Technical Team |
25/06/04 |
Addition of dissent override information. Replacement PSIS Query Response message for all successful responses to PSIS Queries. |
1.2 |
Core Technical Team |
17/09/04 |
PSIS Summary Query removed as not in scope for P1R2. New Queries and Responses for ‘Event List’ and ‘Event’. Renaming of some existing queries and responses. Alignment of queries with generic control act wrapper. All response interactions and messages are for use in P1R2 only; the new response message types do not have HL7 artefact identifiers. |
1.3 |
Core Technical Team |
29/10/04 |
Change requests MIM-CR-0028, 0034, 0089 - 0091, 0093 - 0094. Details of changes made are given in section 10. |
1.4 |
Core Technical Team |
6/12/04 |
Change Request MIM-CR-0270. Removed previous Section 8 - Interaction Index. |
1.5 |
Core Technical Team |
14/01/05 |
New versions of Query Response tabular views and examples. Changed lowercase characters in example UUIDs to uppercase. |
|
|
|
|
PSIS Queries provide a mechanism for clinicians to gain access to the NHS Care Record Spine for an individual service user (patient). Local systems will query the service user’s NHS Care Record and populate screens with NHS Care Record data.
In Phase 1 there are a number of queries as follows:
Dr Michael Franks is in a Consultation with Mr Peter Parker and cannot find the referral letter he sent out to surgeon, Mr Terence Hill, after Mr parker’s last visit.
Dr Franks knows the approximate date of the last visit by Peter so he decides to retrieve the whole of the referral message that was sent to PSIS for onward transmission to Mr Hill.
Michael selects the query option for ‘PSIS Event List’. He is prompted to choose, from a list, the PSIS Event Type he is interested in. He chooses ‘Referral’. He is then prompted to enter the date range during which PSIS Event(s) occurred. The system then performs a PSIS Event List Query and PSIS returns the appropriate list of events via a PSIS Event List Retrieval.
On his display unit Dr Franks is then presented with a list of details for all the referral messages relating to Mr Parker that were sent to PSIS within the selected date range. The listing only shows the PSIS Event, the Event Type descriptor and the Event Time.
(Following on from the above PSIS Event List query storyboard):
Dr Franks looks down the list of PSIS events and selects the Referral Event which he thinks is likely to be the one to Mr. Hill.
This selection prompts the system to perform the PSIS Event Query which retrieves the whole of the PSIS Event contents for that Referral message using a PSIS Event Retrieval interaction. This content is then presented to him in a format which he can read.
Mr. Frederick Harper, a Consultant Haematologist, wants to gain an insight into the clinical circumstances of his patient, Mr. Peter Pan. He has looked after Peter before because of his Non-Hodgkins Lymphoma, however Mr. Harper wants to see if Peter has had any recourse to see a doctor whilst he has been away in the north for the last few months. Mr. Harper elects to query the information held on Peter’s NHS Care Record. His local Trust system has been upgraded to allow access to the NHS Care Record Spine and he can now elect to query Peter’s NHS Care Record in a number of different ways. In this instance Dr Harper chooses to limit his PSIS CRE Query to ask for only the ‘Procedures and Findings’ component of Peter’s record. He also applies a date filter to limit the information return to just the last few months. The query is successful and he is presented with this clinical information within a PSIS CRE Data Retrieval message on his local system.
Mrs Mary Smith takes a tumble and hurts herself when on holiday and visits the A&E department at a local hospital. On her return home, during a routine visit to her doctor, Doctor Bill Jones, she has told him that whilst on holiday last summer in Blackpool she had recourse to see an Emergency Doctor because her leg became swollen and very painful. He decides that he needs to view the clinical data around this problem. He logs onto his local system and requests access to Mary’s NHS Care Record. From a menu option it is possible to make a specific request for a Care Record Event Listing using a PSIS Clinical Statement Query. Dr Jones makes the selection and is immediately prompted to filter the response details by date to reduce the size of the listing returned. As he knows Mary was on holiday sometime in August he enters the date range ‘1st to 31st August 2003’ and then presses OK. The local system then presents him with a list of the Care Events recorded for Mrs Jones during this period. These have been returned from PSIS within a PSIS Clinical Statement Data Retrieval message. He sees that there is one for a Blackpool NHS Trust. He clicks on this item and reviews the other information returned for that encounter.
Madeline Smith has just moved into the area around Newtown. She has lived for the last 10 years in North Town which is the other end of the country. Mrs Smith goes to see her new GP, Dr Mike Canterbury with general pains in her abdomen. As Madeline is a new patient to him, Dr Canterbury opts to query her previous NHS Care Record. He requests a PSIS Event List Query on his local system. However, because Madeline is a new patient and has not registered with the practice, Dr Canterbury does not yet have access rights to view her records. PSIS returns a Query Act Failed message containing the error ‘No Legitimate Relationships exist for the query originator’.
Mr Peter Jones decides that he wants to see what has been recorded in his medical record. He finds out from his GP that he has to write to Dr. Gerald Frederickson, the local Caldicott Guardian, giving his full name, address, Date of Birth and NHS Number details (if known).
Peter does so.
Dr Frederickson, on receiving the letter from Peter Jones, logs onto his local terminal using his ‘superuser’ access. He selects the local patient database and finding Peter on it selects him. The local system performs a PDS Query and Dr Frederickson is shown the updated information.
He then selects the PSIS DPA Subject Access Query function.
The local system prompts for a double check before continuing.
Dr Frederickson then confirms that he wants to retrieve all the held records for Mr Peter Jones.
The local system receives these back within a PSIS DPA Subject Access Data Retrieval message and prompts Dr Frederickson as to storage method. He chooses DVD-RW, carefully labelling the disk and the holder before storing them in his lockable safe. He contacts Peter to arrange a day & time in which Peter can collect his copy.
The applications involved in the PSIS Query processes play specific roles. These, along with the interactions associated with each role, are identified below.
The PSIS Query Placer will initiate any one of the PSIS queries.
PSIS Query Placer Interactions
The PSIS Query Fulfiller will respond to any one of the PSIS queries. A response will either carry data as requested or will be an empty response which carries a reason for there being no data returned.
PSIS Query Fulfiller Interactions
The PSIS Event List Query Started trigger event indicates that the query originator has initiated a query to obtain a list of Events for a specific service user.
The PSIS Event Query Started trigger event indicates that the query originator has initiated a query to obtain a specified Event for a specific service user.
The PSIS CRE Query Started trigger event indicates that the query originator has initiated a PSIS Query for a specific service user.
The PSIS Clinical Statement Query Started trigger event indicates that the query originator has initiated a PSIS Clinical Statement Query for a specific service user.
The PSIS DPA Subject Access Query Started trigger event indicates that the query originator has initiated a PSIS DPA Subject Access Query on behalf of a specific service user.
The PSIS Event List Retrieval trigger event indicates that data has been found on PSIS which satisfies the specified criteria defined in the PSIS Event List Query.
The PSIS Event Retrieval trigger event indicates that data has been found on PSIS which satisfies the specified criteria defined in the PSIS Event Query.
The PSIS CRE Data Retrieval trigger event indicates that data has been found on PSIS which satisfies the specified criteria defined in the PSIS Query.
The PSIS Clinical Statement Data Retrieval trigger event indicates that data has been found on PSIS which satisfies the specified criteria defined in the PSIS Clinical Statement Query.
The PSIS DPA Subject Access Data Retrieval trigger event indicates that data has been found on PSIS which satisfies the specified criteria defined in the PSIS DPA Subject Access Query.
The QUPC_IN180000UK03 PSIS Event List Query Started interaction occurs when a request for a list of the details of all the messages sent to PSIS for a specific patient within a defined date/time range is started. The PSIS Query Placer sends a PSIS Event List Query, with specific query parameters, to the PSIS Query Fulfiller.
Sending Role |
PSIS Query Placer |
|
Receiving Role |
PSIS Query Fulfiller |
|
Trigger Event |
PSIS Event List Query Started |
|
Transmission Wrapper |
Send Message Payload |
|
Message Type |
PSIS Event List Query |
Receiver Responsibilities
Reason |
Interaction |
Query Data Found |
PSIS Event List Retrieval: |
No Query Data Found |
Query Act Failed |
The QUPC_IN190000UK03 PSIS Event Query Started interaction occurs when a request for all the contents of a specified PSIS Event that has been previously discovered by use of a PSIS Event List Query is started. The PSIS Query Placer sends a PSIS Event Query, with specific query parameters, to the PSIS Query Fulfiller.
Sending Role |
PSIS Query Placer |
|
Receiving Role |
PSIS Query Fulfiller |
|
Trigger Event |
PSIS Event Query Started |
|
Transmission Wrapper |
Send Message Payload |
|
Message Type |
PSIS Event Query |
Receiver Responsibilities
Reason |
Interaction |
Query Data Found |
PSIS Event Retrieval: |
No Query Data Found |
Query Act Failed |
The QUPC_IN100000UK05 PSIS CRE Query Started interaction occurs when a request for information from PSIS regarding one or more specified Care Record Elements for a service user is started. The PSIS Query Placer sends a PSIS CRE Query, with specific query parameters, to the PSIS Query Fulfiller.
Sending Role |
PSIS Query Placer |
|
Receiving Role |
PSIS Query Fulfiller |
|
Trigger Event |
PSIS CRE Query Started |
|
Transmission Wrapper |
Send Message Payload |
|
Message Type |
PSIS CRE Query |
Receiver Responsibilities
Reason |
Interaction |
Query Data Found |
PSIS CRE Data Retrieval: |
No Query Data Found |
Query Act Failed: |
The QUPC_IN110000UK04 PSIS Clinical Statement Query Started interaction occurs when a request for information from PSIS regarding one or more clinical statements for a service user is started. The PSIS Query Placer sends a PSIS Clinical Statement Query, with specific query parameters, to the PSIS Query Fulfiller.
Sending Role |
PSIS Query Placer |
|
Receiving Role |
PSIS Query Fulfiller |
|
Trigger Event |
PSIS Clinical Statement Query Started |
|
Transmission Wrapper |
Send Message Payload |
|
Message Type |
PSIS Clinical Statement Query |
Receiver Responsibilities
Reason |
Interaction |
Query Data Found |
PSIS Clinical Statement Data Retrieval: |
No Query Data Found |
Query Act Failed: |
The QUPC_IN120000UK05 PSIS DPA Subject Access Query Started interaction occurs when a request from a service user to return all the care information held on PSIS about him/her is started. The PSIS Query Placer sends a PSIS DPA Subject Access Query, with specific query parameters, to the PSIS Query Fulfiller.
Sending Role |
PSIS Query Placer |
|
Receiving Role |
PSIS Query Fulfiller |
|
Trigger Event |
PSIS DPA Subject Access Query Started |
|
Transmission Wrapper |
Send Message Payload |
|
Message Type |
PSIS DPA Subject Access Query |
Receiver Responsibilities
Reason |
Interaction |
Query Data Found |
PSIS DPA Subject Access Data Retrieval: |
No Query Data Found |
Query Act Failed: |
The QUPC_IN200000UK03 PSIS Event List Retrieval interaction occurs when all the PSIS Event List Query criteria are met and there is relevant clinical data present on PSIS. The PSIS Query Fulfiller sends a PSIS Event List Retrieval carrying the requested Event List to the PSIS Query Placer.
NB: The message type link in the table below provides information for use in P1R2 only.
Sending Role |
PSIS Query Fulfiller |
|
Receiving Role |
PSIS Query Placer |
|
Trigger Event |
PSIS Event List Retrieval |
|
Transmission Wrapper |
Application Acknowledgement |
|
Control Act Wrapper |
Query Acknowledgement Response |
|
Message Type |
PSIS Event List Query Response |
The QUPC_IN210000UK03 PSIS Event Retrieval interaction occurs when all the PSIS Event Query criteria are met and there is relevant clinical data present on PSIS. The PSIS Query Fulfiller sends a PSIS Event Response Retrieval carrying the requested Event to the PSIS Query Placer.
NB: The message type link in the table below provides information for use in P1R2 only.
Sending Role |
PSIS Query Fulfiller |
|
Receiving Role |
PSIS Query Placer |
|
Trigger Event |
PSIS Event Retrieval |
|
Transmission Wrapper |
Application Acknowledgement |
|
Control Act Wrapper |
Query Acknowledgement Response |
|
Message Type |
PSIS Event Query Response |
The QUPC_IN140000UK05 PSIS CRE Data Retrieval interaction occurs when all the PSIS CRE Query criteria are met and there is relevant clinical data present on PSIS. The PSIS Query Fulfiller sends a PSIS CRE Data Retrieval carrying the appropriate Care Record Elements to the PSIS Query Placer.
NB: The message type link in the table below provides information for use in P1R2 only.
Sending Role |
PSIS Query Fulfiller |
|
Receiving Role |
PSIS Query Placer |
|
Trigger Event |
PSIS CRE Data Retrieval |
|
Transmission Wrapper |
Application Acknowledgement |
|
Control Act Wrapper |
Query Acknowledgement Response |
|
Message Type |
PSIS Query Response |
The QUPC_IN150000UK05 PSIS Clinical Statement Data Retrieval interaction occurs when all the PSIS Clinical Statement Query criteria are met and there is relevant clinical data present on PSIS. The PSIS Query Fulfiller sends a PSIS Clinical Statement Data Retrieval carrying the appropriate Clinical Statement to the PSIS Query Placer.
NB: The message type link in the table below provides information for use in P1R2 only.
Sending Role |
PSIS Query Fulfiller |
|
Receiving Role |
PSIS Query Placer |
|
Trigger Event |
PSIS Clinical Statement Data Retrieval |
|
Transmission Wrapper |
Application Acknowledgement |
|
Control Act Wrapper |
Query Acknowledgement Response |
|
Message Type |
PSIS Clinical Statement Query Response |
The QUPC_IN160000UK05 PSIS DPA Subject Access Data Retrieval interaction occurs when all the PSIS DPA Subject Access Query criteria are met and there is an NHS Care Record for the patient held on PSIS. The PSIS Query Fulfiller sends a PSIS DPA Subject Access Data Retrieval carrying the appropriate Care Record Elements to the PSIS Query Placer.
NB: The message type link in the table below provides information for use in P1R2 only.
Sending Role |
PSIS Query Fulfiller |
|
Receiving Role |
PSIS Query Placer |
|
Trigger Event |
PSIS DPA Subject Access Data Retrieval |
|
Transmission Wrapper |
Application Acknowledgement |
|
Control Act Wrapper |
Query Acknowledgement Response |
|
Message Type |
PSIS DPA Subject Access Query Response |
The PSIS Event List Query message allows the Service User to request a list of the details of all the messages sent to PSIS for a specific patient.
The PSIS Event Query message allows the Service User to request all the contents of a specified PSIS Event that has been previously discovered by use of a PSIS Event List Query.
The PSIS Query message requests information regarding a specified Care Record Element within a service user's NHS Care Record.
The PSIS Clinical Statement Query message requests information regarding one or more clinical statements within a service user's NHS care record.
The PSIS DPA Subject Access Query requests all the care information held on PSIS about the service user (patient).
The PSIS Event List Query Response is a response to the PSIS Event List Query and provides a list of the details of those messages received by PSIS, constrained by the chosen Event Type.
The PSIS Event Query Response is a response to the PSIS Event Query and provides the entire contents of the message which is identified by the PSIS Event UUID.
NB: The link below provides information for use in P1R2 only.
The PSIS Query Response message is a response to the PSIS CRE Query and provides the requested Clinical Statements based on the specified query parameters.
NB: The link below provides information for use in P1R2 only.
The PSIS Clinical Statement Query Response message is a response to the PSIS Clinical Statement Query and provides the requested Clinical Statements based on the specified query parameters.
NB: The link below provides information for use in P1R2 only.
The PSIS DPA Subject Access Query Response is a response to the PSIS DPA Subject Access Query and provides ALL the clinical statements from of the service user’s NHS Care Record.
NB: The link below provides information for use in P1R2 only.
Dissent |
This where a patient has not given consent for their records to be viewed by others. |
DPA |
Data Protection Agency |
Event |
Corresponds to the whole message payload, which is the record of the business activity conveyed in the message. This is the granularity at which data is added to and cancelled in a patient record; queries are also supported at Event-level. |
Event Item |
Corresponds to a clinical statement (either simple or compound). This is the granularity at which progression occurs in a patient record; queries are provided at Event Item-level. Event Items are indexed by PSIS using CRE types to facilitate PSIS Query. Note that an Event Item in PSIS may comprise more than one clinical statement - for example, if an Observation statement contains one or more Statement Commentary statements, the PSIS Event Item will be the whole Observation statement including any contained Statement Commentary statements. This is because it is not useful to retrieve or progress a Statement Commentary statement independently of the Observation statement which contains it. |
PSIS |
Personal Spine Information System |
Query Originator |
Clinician or Caldicott Guardian initiating the query |
Service User |
The patient who is the subject of a query |
Tabular views and examples for PSIS Query Responses have been amended to reference the message type artefact id of the data being returned instead of the interaction type.
The example for message QUPC_MT140101UK03, PSIS Event Query, has been amended to ensure all UUIDs are represented in uppercase.