Increasingly advanced tools, data complexity, and unprecedented patient mobility have resulted in a diversity of treatment locations, information systems, and medical-data formats. This multiplicity often poses seemingly insurmountable challenges for a real-time medical record that incorporates patient information from both acute and community health treatment settings.
The dbMotion platform for health interoperability supports these requirements by providing on-demand, secure, integrated medical information that facilitates quality healthcare.
How does using dbMotion’s service oriented architecture (SOA) facilitate health information exchange (HIE)?
How does dbMotion efficiently and effectively create integrated patient records?
What are the highlights of dbMotion's platform?
How does dbMotion support the various deployment approaches of centralized, federated and hybrid architecture?
How does using dbMotion’s service oriented architecture (SOA) facilitate health information exchange (HIE)?
dbMotion’s proven SOA-based platform enables local, regional, and national healthcare providers the flexibility to integrate medical data from a range of technologies and data structures.
The standards-based SOA approach facilitaftes the development and reuse of flexible, modular software services to create highly functional applications. The dbMotion platform is designed to leverage existing systems and applications, without the need for replacement. The infrastructure incorporates data from multiple sources in a variety of formats, and harmonizes the data into a uniform, aggregated, usable structure. Once the information is available in this semantically interoperable foundation, dbMotion software services can display or share it with other applications or relevant “consumers,” such as dbMotion’s web-based Clinical Views or third party applications, including electronic medicals records, personal health records, and decision support systems.
This level of flexible information exchange successfully positions healthcare organizations to address current and future healthcare challenges, such as regulatory compliance, quality measures, and disease management.
How does dbMotion efficiently and effectively create integrated patient records?
dbMotion creates an integrated virtual patient record by securely sourcing medical information across diverse technologies and harmonizing the data for meaningful interpretation and use. This data is then incorporated into a single entity - the virtual patient object (VPO), which is the data object used to mobilize the integrated data to its consumers such as dbMotion’s web-based viewer or third party applications such as EMRs, PHRs, Clinical Decision Support and others.
The Solution shares the integrated data with these consumers and then the virtual patient record is generated according to the organization’s medical and business requirements as well as predefined security policies.
The resulting integrated virtual patient record is viewed by a caregiver as if it were created by a single, universal system.
What are the highlights of dbMotion's platform?
dbMotion's features provide essential benefits that meet healthcare enterprise needs in the short and long term:
All-encompassing solution – Facilitates access to a comprehensive, integrated virtual patient record based on a complete product set – ranging from data integration tools to innovative workflow applications. Covers a broad set of needs and use cases, developed by and for physicians and other healthcare professionals.
Foundation for semantic interoperability – Exchanges, integrates and displays harmonized data that represents the clinical information’s inherent meaning.
Integrated virtual patient records – Seamlessly connects disparate healthcare systems to create an integrated virtual patient record viewed by caregivers as if it were created by a single, universal system.
Vocabulary management – Enables harmonization and unification of medical information from disparate data sources and systems by mapping industry standards and coded systems, facilitating better medical interpretation.
Clinical viewer/portal – The patient-centered clinical viewer present essential patient information to streamline and accelerate physician and caregiver workflows.
End-to-end security – Offers features such as authorization, authentication, patient consent, as well as secure data transfer, encryption and digital signatures.
Tracking and auditing – Provides logs, tools and applications that record system and caregiver activities.
International support – dbMotion provides international support for language, date and time formats.
Robust, SOA-based platform for interoperability – Enables the utilization of existing systems and the development of new applications to address key healthcare business objectives such as quality measures, compliance, disease management and more.
Open, standards-based system for data integration – Integrates applications with no dependencies, limitations or need for modifications, whether based on standards, guidelines (e.g., IHE) or proprietary interfaces.
EMR integration – dbMotion can integrate with external EMR systems to expand their scope of clinical data. Healthcare providers can update their EMR systems with enterprise-based clinical data from dbMotion, making their medical records more complete and eliminating the need to re-access that data every time it is needed.
EMR and workflow synchronization – dbMotion supports single signon (SSO), enabling streamlined context synchronization. It also enables the embedding of clinical data and web components into existing applications, such as EMRs.
Improved clinical & business outcomes – Access to the comprehensive virtual patient record helps improve quality and reduce redundant and unnecessary testing. Leveraging existing systems avoids costly replacement and disruption of workflows.
Scalability – Can be deployed in any single healthcare organization and easily expands and connects to regional and national networks.
Flexible implementation approaches - Supports centralized, distributed and/or hybrid health information exchange.
How does dbMotion support the various deployment approaches of centralized, federated, or hybrid architecture?
dbMotion’s architecture overcomes the challenges of scalability, information ownership, security, and privacy inherent to a healthcare enterprise’s vast array of organizations, facilities, standards, and IT systems – regardless of the organization’s information storage and sharing approach.
Centralized
A centralized dbMotion implementation uses a singular persistent repository to store data originating from an organization’s clinical and administrative systems.
This centralized configuration is a foundation for system scalability, supporting data acquisition from newly added systems and facilities, allowing uniform system management policies for different enterprise members. It also enables easy connections with external HIEs, networks and independent clinical systems and data providers.
Federated
A federated dbMotion configuration has more than one physical location (node) for data storage. It serves the needs of multi-stakeholder organizations in which data ownership is distributed. This dbMotion configuration provides solutions to the complex issues of data collection, diverse facility security policies, and management of user and role definitions for each of the health network’s decentralized nodes.
To launch a self-running presentation demonstrating a federated dbMotion architecture click here.
Hybrid
The hybrid dbMotion architecture sets the foundation to easily scale an organization’s health information exchange. The hybrid approach combines the characteristics of both the centralized and federated architectures to accommodate enterprises that have a mix of centralized and decentralized nodes. For example, an organization can begin with a centralized approach for its internal requirements and as the need emerges to connect with independent data providers, autonomous nodes can be added as necessary.