When PatientLocate is used to identify patients at a specific healthcare facility, Patient Precision dedicates a PatientLocate computer server to hold patient data generated by that facility. The PatientLocate server is configured and managed remotely by Patient Precision personnel, with no maintenance required by provider IT staff.

The PatientLocate server can be a physical computer system or a virtual server, deployed in either the healthcare facility’s data center or the PatientLocate data center. No matter where and how the PatientLocate server is deployed, all protected health information (PHI) physically remains on the server, and is never transmitted elsewhere. As an additional layer of protection, all personal patient information is encrypted when stored in the PatientLocate database.

The PatientLocate server operates by building patient profiles from real-time clinical data produced by healthcare providers’ clinical information systems. This data includes demographics, observations, labs, orders, prescriptions, and procedures. Data is typically made available through the industry-standard HL7 protocol supported by all major Electronic Medical Record vendors.

The first time PatientLocate is used to identify patients at a healthcare provider facility, Patient Precision personnel work with the provider’s IT staff to obtain a copy of the data already being communicated among the facility’s IT systems. No new interface programming is ever required to deploy PatientLocate. Instead, Patient Precision’s technology allows the PatientLocate server to adapt to the provider’s unique data environment.

Once adaptation is complete, the PatientLocate server can begin to identify patients for the study. Identifying patients for the first PatientLocate study at a research site can typically begin within 1-2 weeks after the PatientLocate server is deployed.