| Table of Contents | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
EMIS is a general practice electronic medical record system in the UK. You can set up an automatic data transfer for a GP practice's patient data from EMIS into PKB using the EMIS Patient Data Extract Service (PDES). The transfer can only begin with the permission of a GP who is a data controller of the GP practice. The data controller must formally sign the contract authorising the data transfer and they can stop authorisation at any time in the future.
...
To set up your GP practice for automatic transfer of your patients' data please contact the PKB team.
The PKB team will help your GP practice to set up their PKB site, and activate the extract service. Once the service has been activated the GP practice professionals will be able to work with their patients in PKB and view the EMIS data there.
...
Log in as a professional to PKB.
Click on Go to view the patient list and choose a patient's record to enter
Click on Edit to view the patient demographics
...
Click on Health>Diagnoses to view EMIS diagnoses.
...
Click on Health>Allergies to view EMIS allergies.
...
Click on Treatment>Medications to view EMIS medications.
...
Click on Health>Measurements to view EMIS measurements.
Click on Health>Tests to view EMIS test results.
Click on Sharing>Professionals to view the teams the patient is sharing with and the level of access.
...
Note: if the patient is sharing with teams or has manually entered data this will also be available in PKB. A GP team will only see data with the PKB privacy label that they have access to, or that they have entered themselves manually.
...
Activating the sharing agreement for that GP practice within EMIS.
Operational checks by PKB to ensure that the extract processing was passing all tests to allow extract processing. This occurred before the GP practice started their testing process.
Setting up test patients on the local EMIS web instance.
Processing of the extract was enabled for these the test patients only.
The test patients were created on an EMIS specific test environment within the n3 network.
Following a test plan to review the appearance of these patients' data within PKB's user interface and comparing with the same patients within EMIS. Checks included:
New patient records created in PKB where required. All data have been transferred correctly for a patient. No incorrect data is in PKB and no extra data is in PKB incorrectly attributed with EMIS / the practice as the source. (There should still be non-EMIS data of course from other providers looking after the patient as well as the patient and carers.)
Additions of data subsequent to initial data sent are reflected correctly in PKB.
Updates or deletions of previously sent data result in an update on deletion in PKB.
No sensitive data in EMIS (as per the SCR sensitive exclusion list or other exclusion list) is included in PKB.
Initially this focus was on patient creation and processing allergies, diagnoses and medications.
The testing plan signed off with these customers is available at this link and the accompanying screenshots can be reviewed in this document. The test number on the test plan corresponds to the test number in the screenshots document.
...
PKB processes a subset of files to transfer data which includes:
First Stage
Second Stage
...
Medications
Allergies
Diagnoses
Measurements (subset for Physical Health Checks)
Not Available
Care Plans - (collaborate in PKB)
Alerts
Consent (controlled by PKB)
Document (no free text)
Investigation - CareRecord_Observation (GUI Dev)
Family - CareRecord_Observation (GUI Dev)
Risks and Warnings
...
PKB currently processes the extract to create and update demographics, allergies, diagnoses, medications, and NHS Health Check measurements and lab test results.
...
If a patient was created in PKB already by another organisation but is not registered, it's possible to update their records from your GP practice extract but they will not be added to your team until the creating organisation facilitates this. If you have questions about this process please contact the PKB team
Diagnoses, allergies and medications
PKB creates and updates diagnoses, allergies and medications using the clinical codes received from EMIS. For diagnoses PKB will look-up the received SNOMED CT code in order to determine the privacy label, and data type to apply. For allergies PKB will apply a 'general health' privacy label, and will look-up the received SNOMED CT code in order to determine the data type to apply.
PKB has published the coding tables online in our developer wiki. Please contact us if you have feedback or suggestions.
...
For a full list of measurements that are added to records, please see this spreadsheet.
Tests
For lab tests, PKB will look up the received Snomed CT code to determine the privacy label, and data type to apply.
Snomed CT codes for lab tests are mapped to LOINC codes. This means the tests will appear in patient records on the same graph as other tests that have been mapped to LOINC codes and it is possible to include them in care plans.
For a full list of lab tests that are added to records and their mapped LOINC codes, please see this spreadsheet.
EMIS extract service data exclusions
...
4 x SNOMED ref sets excluded by EMIS and not sent to PKB:
These lists also apply to codes sent in HL7 messages. PKB filters the data received and skips these
Additional sensitive code set. This is list of Read V2 and EMIS proprietary codes our customers favoured excluding. This list will apply to codes sent from the EMIS extract service, or sent in HL7 messages. PKB filters the data received and skips these. This list is also available on the coded data page.
Additional SNOMED ref set exclusions by PKB:
These lists also apply to codes sent from the EMIS extract service, or sent in HL7 messages. PKB filters the data received and skips these.
...