While exhibiting in 2010 and again 2011, at the Healthcare Information Management Systems Society (HIMSS) annual convention, we had the iconic Delorean from the Back to the Future movie franchise in our booth. This was part of a fundraiser for TEAM FOX benefitting the Michael J. Fox Foundation for Parkinson’s Research.

Read more about it here.

As our needs for complex workflows, custom user interface gadgets, and more were added to our system, the Quizlets technology was getting pushed to its limits. Rather than continue pushing, we created a new version of the concept, where interface, business rules, and data all existed within a living document, known as L337 (pronounced “Leet” – short for “Elite”) Forms.

This new technology once again eased the development, review and deployment process of new or even simply newly-revisioned forms. L337 Forms were used by the Michigan Health Information Network (MiHIN) with their Health Reimbursements Arrangements (HRA) project, which took a CCD Document as its original data source, and then created a user interface leveraging data points within the base CCD as well as environmental and application data, and creating a living form that was able to generate a corresponding HRA formatted output at any time.

We began working with Clinical Architecture on the Social Security Administration E-Disability project. Soon after, we established a closer working relationship, leveraging our Alchemy product’s ability to ingest and output multiple different data formats (HL7, CCD, etc.) and their ability to map between multiple data dictionaries (ICD-9, CPT-4, etc.). We quickly realized that a combined solution would solve many interoperability hurdles faced by healthcare today, causing launch of PIVOT. We have since assisted in furthering their PIQI Framework by creating a PIQI document from any PIVOT (aka Alchemy) source.

After 10 years of being in business at Reliance Software (RelWare), we took a look back at our accomplishments to that point, and made a set of marketing slicks, as they were called, to showcase them. This was the first, focusing on the 10 years themselves.

Order Entry software for hospital-based and provider-based patient orders

Read more about it here.

built to replace the outdated Visual Basic (VB6) WebClass Architecture

Tested and Certified by Microsoft as a .Net Application Engine

Ran EXR/CPNG for dozens of interface engines as well as the main web-based application engine.

Read more about it here.

In 2004, we partnered with the Henry Ford Health System to rewrite their internally built electronic health record application, known as “Care Plus.”  We were at a technological point with CDR-Web, where we also wanted to do a rewrite, utilizing Microsoft’s new .Net technology.  

With this partnership, we worked with their teams plan and facilitate a zero-data-loss migration of 10 years of clinical data, as well as write a new world-class Electronic Medical Record.  The end result was known at HFHS as CPNG or “Care Plus Next Generation” and commercially as RelWare’s EXR.

EXR was Certified for “Complete EHR, Inpatient” and “Modular EHR, Ambulatory” by InfoGard Laboratories EHR Certification Body under Meaningful Use January 2011.

Read more about it here.

In 2004, we began a partnership with Henry Ford Health System (HFHS). We were at the start of a massive rewrite to our Electronic Health Record software, CDR-Web. HFHS was looking to replace their current system, CarePlus, which had numerous points of source data as well as several spin-off applications. The partnership resulted in CarePlus Next Generation for them and EXR for us.

Read more about the partnership.

Making custom forms for a web-based environment was a tedious exercise, back in the day. Our team looked at the standard form, and mapped them to XML objects. We then had the XML store the value of the corresponding UI item (textbox, slider, radio buttons, etc.), allowing the XML document to be a representation of both form and data, requiring only a simple library to render the form in a web browser, and allow a user to update. This led to adding digital signatures and allowing for complete workflow systems to be created, forcing “Manager Co-Signatures” and more, based purely on rules determined within the form.

 A comprehensive, hospital-based computerized physician order entry (CPOE) with real time interaction checking against patients know medications and allergies