In order to determine whether OpenHIE is right for you and your requirements it is first necessary to state what OpenHIE is not.
Though OpenHIE contains a Functional Specification for a Shared Health Record (SHR), and is meant to contain patient health information (PHI), it is not an Electronic Health Record (EHR). It is likewise not a point-of-service (POS) application, though it does provide services and PHI for a POS application, and those services that provide direct patient care.
Similarly, it is not a Laboratory Information Management System or Pharmacy Information System, though it does provide access to data that is contained within the SHR repository for accessing a patients' lab and pharmacy related information.
If your requirements indicate that there is a need to transmit and exchange PHI securely among different systems, and to provide for the near real-time flow of referrals, encounters, and orders between systems, then the OpenHIE platform and components may be right for you.
The OpenHIE Architecture & Standards provides for the integration of services and interfaces to PHI source-of-truth, but more importantly it also provides a community of like-minded individuals and organizations in a Community that seeks to grow and support OpenHIE as a standards-based, future-proof open source platform for enabling 21st century healthcare.