We are proud supporters and partners with the originator of the new PIQI Framework, Charlie Harp of Clinical Architecture. We also built the first system to generate PIQI formatted output, allowing systems using our Canonical Model, like Alchemy and PIVOT, to create PIQI scoring datasets from their clinical sources.

Learn more about Clinical Architecture.

Leveraging the power of the ISO 20022 standard, we are allowing providers and payers to work together to make Fast Payment Processing available. Using our underlying technologies of Alchemy, we integrate Invoices (X12, EDI, etc.) with Proof of Service Documentation (CCD, CDA, etc.) to generate a single packaged claim for review and submission. Once authorized, it is released to the financial network and allows for immediate transfer of funds.

Talk to us to learn more about this exiciting new standard and process.

Our partner Clinical Architecture has a solution for analyzing and cleaning clinical data. At the heart of that solution beats our Alchemy engine, converting all of their inbound data into our Canonical Data Model, which allows their system to perform in-depth analysis of all of the datapoints, and then send them back out in whatever clinical data format is required.

Read more about it here.

Arcana is a robust population registry. Unlike many EHRs, it stores all data discretely. It provides population level views for your reporting and monitoring needs with point and click ease.

Coupled with Alchemy, Arcana accepts all electronic data formats, and aggregates clinical data from any system in any format, at your need. Easily configurable and highly manageble, no data, regardless of size or format, is discarded. You gain huge benefits from unparalleled reporting, with a data depth that you require, and regardless of changes in specifications from governing organizations.

Arcana brings an unparalleled ease of use into your reporting. Anyone can review and create population measures or ad-hoc queries with Arcana’s build tool, giving a complete breakdown of the results, and the individuals, both matching and missing. Unlike other registries and EHRs, all data that is normalized into Arcana is discrete and available for reporting. Arcana also provides real-time dashboard views of any subset of a users population. This can be by facility, care team, or direct patient association.

With Arcana, organizations gain immediate insights for potential gaps in care within their patient populations. Arcana supports care and disease management functions; assists in medication reconciliation, and reduces the cost of care.

Contact us today!

Alchemy provides a “Rosetta Stone” service for clinical data. It acts as a translator and harmonizer for fragmented and inconsistent healthcare information. Alchemy is able to break each source data format down to its elemental data points, and then generate back out the same data in any different format, or even the same format, but consistent and more importantly, correct. As most healthcare technicians are aware of the saying, “When you’ve seen one HL7 message, you’ve seen ONE HL7 message,” the same is true with most data formats. Alchemy is able to understand them all, giving itself the tagline, “It turns your healthcare data into gold.”

Alchemy is the heart of our partner Clinical Architecture’s PIVOT service offering, and Michigan Health Information Network (MiHIN) was an early adopter of Alchemy techonology, as it helped power some of their services (read more here).

Contact us to see how Alchemy can help you.

MiHIN is Michigan’s statewide network of connected hospitals and physicians, allowing for the secure sharing of healthcare information between organizations.  In 2012, partnered with SEMHIE, we joined the MiHIN group of approved Quality Organizations (QOs). As a QO, we provided interconnectivity and messaging services for a number of Physician Organizations (POs), providing ADT Notifications, Statewide Lab Notifications and Medication Reconciliation Services. These services continue to run for select POs, now thirteen years later, and have totaled hundreds of millions of HL7 messages and CCD documents.

As openAirWare, we also worked directly with MiHIN as external interoperability and subject matter expert consultants. Some of the projects completed with MiHIN were a CCD Trimmer service, allowing for the removal of unauthorized portions of a CCD document; a CCD to Blue Cross Gaps-in-Care conversion service (a pre-cursor to our Alchemy service); and Diretto, their secure healthcare messaging service.

This press release from MiHIN describes some of the potential of Alchemy.

A Data Model defines layout and structure of how all data is represented and perceived.  Our Data Model, known as the “Parsed Data Block” is a well-defined XML based structure, that allows us to map any known data point for a given patient message (i.e. CCD/CDA, HL7, FHIR, CSV) to a specific spot in the Data Model (see example below).

For instance, when looking at a message with our Parsed Data Block, the name of a patient will always be found at the XML Path: /Document/Patient/Name and having possible attributes like first, middle, last and so on, regardless of what type of message was given.  Paths like this exist for each and every possible piece of patient data.

After years of working with the various healthcare standards, we have mapped most every data source type into and back out of our Canonical Model. We have packaged these libraries and several tools into our Alchemy system, “turning your healthcare data into gold.”

This allows us to immediately convert ANY source data from its original state INTO our model, perform any work we want on it, and send it back out either as the original format, or even as a different one. 

The beauty of this design is that once it is in the Canonical Model, any developer that understands basic XML can then work with the data, and either build triggers, modifiers, or analysis tools.  That’s why partners like MiHIN and Clinical Architecture chose Alchemy.

<Document source="CCD/CDA" title="Continuity of Care Document" effective="12/06/2009 13:00:00">
  <id root="6858a017-39c1-4153-bbd4-eaedac72a0e7" />
  <Code code="34133-9" name="Summarization of episode note"/>
  <Patient>
    <id root="2.16.840.1.113883.4.1" ext="999-99-9999" />
    <DateOfBirth precision="DAY">11/01/1972 00:00:00</DateOfBirth>
    <Name first="Charles" middle="A" last="Test" />
    <Gender code="M" name="Male" coding-system="HL7 AdministrativeGenderCode" />
    <MaritalStatus code="M" name="Married" coding-system="HL7 MaritalStatus" />
    <Religion code="1072" name="Full Gospel" coding-system-code="2.16.840.1.113883.5.1076" />

When moving from the hospital-focused solutions that we created as Reliance Software Systems, we re-branded as openAirWare and expanded our focus. We continued developing healthcare software solutions, but also wanted to be able to assist other communities. A year later, in 2012, we created a “Vision Diagram” (see below) to plan out where and how our services could be utilized. In 2016, we updated it, having everything being the same as it originally had been, but now with actual product and service offerings behind them. We have since started to enter our third decade of software solutions for healthcare, we decided to go back to our roots, unifying our solutions and services from both Reliance and openAirWare to a single brand, RelWare.

Read more about our history here.

We have operated as the technical arm of the SouthEast Michigan Health Information Exchange (SEMHIE) since its inception in 2010. Our first project was the Social Security Administration’s nationwide E-Disability service. In 2012 we joined the Michigan Health Information Network (MiHIN) group of approved Quality Organizations (QOs). As a QO, we provided interconnectivity and messaging services for a number of Physician Organizations (POs), providing ADT Notifications, Statewide Lab Notifications and Medication Reconciliation Services. These services continue to run for select POs, now thirteen years later, and have totaled hundreds of millions of HL7 messages and CCD documents.

An XML-safe templating language created for manipulating blocks of XML using string-based templates.

X2TL is an XML-safe “mustache” templating language, written in C# .Net. It was written as a software development tool, now being offered open-source. This library has been tested and used in several enterprise production applications. Check out the printable X2TL Language Reference Guide.

Made open source by the author, August 2016 under the MIT License. Now available at: https://github.com/openAirWare/X2TL and https://bitbucket.org/openAirWare/x2tl