OmniClinic works through custom integration with EMR databases. This may include, as needed, HL-7 integration. OmniClinic uses its own database to store the data it receives. This database is optimized for display of data and for mobile performance. The HL-7 messaging can be handled by a variety of interface engines. We typically build the necessary interfaces ourselves using an integration solution of our choice, but we can also use one that the customer owns, if necessary. The typical installation requires a server (hard or virtual) at the hospital or healthcare institution’s datacenter, which communicates securely with the main OmniClinic server. The main server handles user identification and access into the system. If the hospital does not have its own datacenter, the hospital-side server can be installed with a hosting provider of the hospital’s choosing, or can be hosted by iLabs Medical.
-
iLabsMedical Entrepreneurs say the FDA is killing medical innovation t.co/b1tQfTjVNj via @VentureBeat

-
iLabsMedical (The problem, and why we build OmniClinic): Hospitals lose $8.3B using old technology #HIT #mHealth #HIE t.co/G6aiqBnTlC

-
iLabsMedical This is why we are building OmniClinic: A plea for a universal, unified EMR t.co/TjUVhgn4Xr via @kevinmd #OmniClinic #HIE

-
iLabsMedical Integration of a Mobile-Integrated Therapy with Electronic Health Records: Lessons Learned #HIT #mHealth t.co/Z4b3iHRgXY

-
iLabsMedical Trinity taking leap of faith toward cloud #HIT t.co/rAMxYxVn2v
