We file GP2GP on EMIS for your entire practice once every day at no extra cost ✨
What does this do for you?
By automating the filing of unfilled GP2GP tasks, we are reducing manual work for you and eliminating delays in processing patient records. 🏃♂️
✅ How it works:
Filing GP2GP records: Every 24 hours we take care of all the pending unfiled GP2GP records that are waiting in your task list - no manual intervention needed.
‼️ What we don't do:
Degrade tasks (medications, allergies, events): These tasks are not processed automatically. You’ll still need to manually handle these items if they appear in your task list.
How we file GP2GP
When we file GP2GP records, we select the option to ‘file into the patient’s record and create degrade tasks when required’.
The practice will still need to action the degrade tasks (like medications, allergies, and events) as usual.
We believe it is clinically safer to 'File as record with tasks'. However, if your practice prefers to 'File as record' please contact the support team ([email protected] or live chat on the bottom right 👉 )
How to give us access for GP2GP filing
To allow us to file your GP2GP transfer, you need to grant Global Viewer access to each of our smartcards.
We’ve put together a short video that shows you exactly how to do this. The video includes example names and smartcards, which will differ for each practice. You can find the smartcards you need to set this up in the Hub, under Settings > Smartcards.
You can confirm whether Global Viewer access has been successfully enabled by going to ⚙️ Settings > GP2GP on the Hub.
By default, all practices are set up to allow GP2GP filing. If you prefer to opt out, you can do so under Settings > GP2GP 👆.
What might cause GP2GP to fail?
Although most unfiled GP2GP tasks will be filed successfully, there are some cases where it can’t be processed automatically or manually🙅♀️:
Patient death or inactive status
Duplicate filings (someone else has already initiated filing the record)
Data issues (demographic records under investigation at Spine)
Technical issues (known bugs, or issues with SCR consent)