Data Sharing: The Process
This article will provide a brief overview on how Apex allows reporting across multiple organisations, whether a PCN, Place or ICB Enterprise organisation. Apex Enterprise organisations are able to view data across whole areas depending on active data sharing agreements and the practice Apex having shared Service definitions. This data does not include patient level information or individual clinician names.
Establishing Data Sharing
In order for us to begin and establish an Enterprise view for your PCN, Place or ICB, we will require a signed MOU from each practice authorising data sharing from the practice to the Enterprise. We can share a Sample MOU for you to customise with your own details. All we need from an Apex perspective is a record of consent to show each practice agrees to share data via the application, but remembering at all times, information is pseudonymised and aggregated to a practice-level - no clinician or patient level information is shared.
The establishment of an Enterprise organisation is of no additional charge. Please contact deployment@edenbridgehealthcare.com with signed MOUs to progress your Enterprise organisation.
Understanding Data Sharing
The below diagram demonstrates how data is streamed firstly from the practice clinical system into the Apex platform, and can then be shared with Apex Enterprise organisations. Once the above step of establishing data sharing has been complete, practice level users will need to enable data sharing within their Apex to allow the Enterprise reports to be populated with relevant data.
Key
This includes community/hub instances of the above clinical systems. Installing with these organisations is an advantage when reporting on activity, such as Enhanced Access, across the entire PCN.
Each arrow represents an active data stream from the clinical system, which is responsible for providing pseudonomysed appointment, patient and clinical activity data to the Apex platform.
Each green symbol represents an instance of Apex. If you have access to multiple Apex organisations, you can use one log in for this and navigate between the organisations by clicking on your name in the top right corner.
The dotted lines represent an active data
sharing agreement well with
the Enterprise organisation, as as Service definitions having been configured and independently shared. Sharing with Enterprise organisations is granted on a case-by-case basis, so it is possible to share data with a PCN for example, and not an ICB.
PCN instances of Apex do not have data sharing functionality with other Enterprises, such as Places or PCNs, therefore all mapping takes place within practice level Apex.
Accepting Data Sharing Agreements
Once we have created an Enterprise organisation and linked up the relevant practices, each practice will be able to view and accept a Data Sharing agreement in Apex. A user with system administrator level access will be able to action this within their own practice view of Apex. This can be actioned by navigating to Settings > Data Sharing. Click on the ‘Sharing Data’ tab at the top to view organisations that can be shared with.
Click ‘Change Permissions’ and click on the toggle to turn the agreement on or off.
Sharing Appointment Data
In order to populate the Enterprise organisation with appointment data, Services will need to be shared with Enterprise to allow individual definitions of activity to support aggregate level reporting. This configuration is complete within practice level Apex to allow those who most understand appointment book setup can ultimately ensure accuracy in reporting and the ability to account for individual ways of working.
Useful Links
Related Articles
FAQs: Data Sharing & Access
Please view our collection of frequently asked questions during training and via our support desk. If you wish to discuss any of your queries in further detail, please open a ticket here. You can also join our Facebook User Group for further ...Data Status Support | EMIS Extract Never Complete/Sharing Agreement Requires Activation
During the early stages of Apex utilisation for practices who use EMIS Web, the EMIS Partner API will be configured during your first remote call. This data source will stream appointment data overnight for analysis in the system. Following this, in ...Data Sharing: A Guide for Practices
We appreciate that many users of Apex have concerns during their early deployment regarding data sharing and access. We have collated a timeline of what, if any, data is shared via your Apex organisation and what requirements must be met in order for ...Appointment Data | Building and Amending Services
Overview of Service Configuration Many of the Apex dashboards and reports are driven by the Service selected in the drop down menu at the top, such as Appointment Activity in Access & Demand. Each Service visible in the menu is associated with a ...Data Status Support | EMIS Partner API and EMIS Extract | Requirements & Troubleshooting
The installation of the Apex software typically takes place in a 20-minute remote call. This may differ slightly between areas depending on local IT processes regarding the installation of software so we will advise accordingly. For EMIS practices, ...