HAPI (HL7 application programming interface; pronounced "happy") is an open-source, object-oriented HL7 2.x parser and encoder for HL7 version 2.x messages written in Java. This project is not affiliated with the HL7 organization; we are just writing some software that conforms to their specification. The project was initiated by University Health Network (a large multi-site teaching hospital in Toronto, Canada).
You can use the category filters given on the right sidebar to narrow down your search results.
- Axial 360 is an interface engine and connector library that enables health care systems of all types - hospital systems, lab systems, EHRs, HIEs, etc - to share clinical data when it is needed.
- Axial 360 is built using best-of-bread open source components that enable improved scalability, extensibility, and modularity relative to other interface engines.
- Axial 360 will feature a library of free “connectors” developed by the open source community, that will reduce the time required to interface with applications.
The IHE Cross Enterprise Document Sharing (XDS.b) integration profile facilitates the registration, distribution and access across health enterprises of patient electronic health records. XDS.b is focused on providing a standards-based specification for managing the sharing of medical summary documents between any healthcare enterprise, ranging from a private physician office to a clinic to an acute care in-patient facility.
FreeSHIM is an opensource electronic medical device interface, which aims to allow any EMR/PM system to talk to any medical device attached to a workstation without having to install tons of pesky drivers or “reinvent the wheel” for each additional device manufacturer.
It is written in Java, and has been tested on Linux and Windows workstations (though we’re pretty sure it also runs fine on Mac OS X as well), and exposes both SOAP and REST interfaces. Its only prerequisite is a running J2EE container, such as Apache Tomcat.
This project holds an implementation of the Cross-Enterprise Document Sharing (XDS) profile as defined by IHE (ihe.net). It includes implementations of both the Document Registry and Document Repository actors.
The project is deployed at the XDS Public Registry Test Facility of the National Institute of Standards and Technology (NIST).
Aurion is an open source health information exchange platform that implements the Nationwide Health Information Network standard services and content specifications. Aurion is the first project chartered through the Alembic Foundation. This software enables the secure exchange of interoperable health information among diverse organizations using a wide variety of technologies.
ATNA is an IHE security profile representing Audit Trail and Node Authentication. OpenATNA is an implementation of an Audit Record Repository supporting RFC 3881 audit messages over BSD Syslog as well as RFC 5424-5426 (UDP and TLS).
- Optimizes the database so that entities such as active participants, audit sources, participant objects and codes are not duplicated for every message received.
- Performs validation of messages as they arrive.
- Optionally logs errors as well as audit messages.
- Supports TLS and UDP.
Dicoogle PACS is a distributed medical image system and offers the following features:
Laika analyzes and reports on the interoperability capabilities of EHR systems. This includes the testing for certification of EHR software products and networks.
To support EHR data interoperability testing, Laika is designed to verify the input and output of EHR data against the standards and criteria identified by the Certification Commission for Health Information Technology (CCHIT). Laika is used by the Certification Commission to perform part of the interoperability certification inspection of EHRs.
The Project HealthDesign Common Platform is a set of software components that provide common, shared functions to a variety of personal health applications (PHAs). The goal of “centralizing” these functions is to reduce personal health application implementation time and increase interoperability among the PHAs. The common platform components are currently implemented as web services that PHAs may access via standard web interfaces. Services exist for storing observations and medications, as well as for providing authentication, registry, and access-control functions.