The HYBRID Generic Clinical Registry Platform innovation presents a radical change in registry development. The new platform is not an enhanced version of our previous technologies. This is a fundamental shift that will change the clinical registry market by providing a modern platform for clinical registries for years to come!
Cloud-based, generic, meta data driven clinical registry development platform
Based on ARMUS’ patient centric, enterprise level architecture
Complete solution for any clinical registries and data warehouses
Complete back-end integration with ADT, device and EMR interfaces
Built-in data version support
HYBRID is a Generic Platform
HYBRID doesn't have any specific registry terms in the codebase at all - ARxML is used to describe all of those associations, allowing for great flexibility in modeling any registry without needing any modification to the basic code.
Flexible to Evolving Registry Standards
All HYBRID registries are defined by ARMUS’ Clinical Registry Specification Markup Language (ARxML) providing unmatched flexibility to follow new requirements. Using the ARMUS Script language library, domain experts can define all business rules (enabling conditions, validations, default values, data ranges, etc.) for any elements of any dataset. This also means that defining a new registry or adding a new elements to an existing registry consists of creating or modifying an XML file based on ARxML instead of writing custom code for each individual registry or field.
Fast Dataset Iterations
A registry is published in HYBRID by uploading a valid ARxML file. When this XML file is uploaded to HYBRID, the registry is available immediately for data collection. This provides fast iterations of registry developments by allowing the user to see the current state of each registry and making modifications that can be visible immediately upon successful upload of a registry specification file.
Data Validation for ALL Incoming Data
The HYBRID architecture allows the validation of incoming data in all application tiers using the ARMUS Script language. This ensures that ALL incoming data (entered via a UI or transmitted via any device interface) can be validated where it is most efficient using a set of rules that were specified just once.
Multiple Specialty/Registry Support
HYBRID is designed to host multiple registries within a single database, therefore it is possible to maintain a clinical database with more than one clinical specialty and allowing for sharing of data among registries, as applicable. This also means that users can be trained on just one software system to manage all registries.
HYBRID supports user privileges for each registry so that each user can only see those registries that they were granted access to.
Occurrence Data Security
HYBRID also supports partitioning occurrence data so that it is possible to configure different business entities that can each see and manipulate their own data, while also allowing a parent organization to see its child organizations’ data.