You are here

Project Wizard

You can use the category filters given on the right sidebar to narrow down your search results.

Utilities For Patient Data Exchange (UPDE)

Rating: 
Your rating: None Average: 4.5 (2 votes)

Utilities for Patient Data Exchange. A parser for text files to use with some of the utilities provided by the DCMTK from Offis. The purpose is to provide a basic DICOM Modality Worklist Management SCP.

JCAM Engine

Rating: 
Your rating: None Average: 3 (2 votes)

XML Validation Framework and Canonical XML dictionary-based exchange assembly - OASIS CAM

The OASIS CAM toolkit provides a suite of tools for XML Validation and XML Exchange design and assembly from canonical XML dictionary components.

Included in the toolkit is an XML Editor/Validation/Schema Designer along with the CAMV runtime XML validation engine.

The project implements the OASIS CAM standard & NIEM IEPD approach. The visual editor allows design of exchange structures using XML components dictionaries.

Aurion

Rating: 
Your rating: None Average: 5 (2 votes)

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.

Indivo

Rating: 
Your rating: None Average: 3.4 (5 votes)

Indivo is the original personally controlled health record (PCHR) system. A PCHR enables an individual to own and manage a complete, secure, digital copy of her health and wellness information. Indivo integrates health information across sites of care and over time. Indivo is free and open-source, uses open, unencumbered standards, and is actively deployed in diverse settings, in particular our own Children's Hospital Boston and the Dossia Consortium.

OpenHRE

Rating: 
Your rating: None Average: 1 (5 votes)

OpenHRE is the world's first open source toolkit that provides a standard and secure means to exchange data between existing health records systems. With OpenHRE, health professionals can locate, access, and review clinical data related to a specific health consumer, or acquire de-identified clinical data for population studies.

Axial 360

Rating: 
Your rating: None Average: 2.3 (4 votes)
  • 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.

Model-Driven Health Tools (MDHT)

Rating: 
Your rating: None Average: 4 (3 votes)

Open Health Tools Model-Driven Health Tools (MDHT) Project is a wide-ranging open source effort to promote interoperability in healthcare infrastructure. It promotes shared artifacts between related healthcare standards and standards development organizations, and works to develop localized specifications. It also delivers a common modeling framework and tools that support seamless integration of design, publication, and runtime artifact creation.

HL7v3 Test Harness

Rating: 
Your rating: None Average: 2.3 (4 votes)

"The HL7 Test Harness system is an HL7 v3 message conformance testing application that also provides the ability to simulate the message processing actions of a client and/or server system. The app provides message workflow, format and content testing."

Project HealthDesign Common Platform

Rating: 
Your rating: None Average: 2.3 (3 votes)

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.

epSOS Common Components

Rating: 
Your rating: None Average: 3.7 (3 votes)

The epSOS project has released interoperability specifications (Common Components Specification) for national Contact Points (NCPs) to interact and support epSOS defined services such as patient summary and prescription. epSOS has also established a testing process for testing compliant implementations of these specifications, and ensure their interoperability.

Pages