BPM+ Value Proposition
Why choose the Business Process Modeling Plus (BPM+) Approach?
Current State
Delivering consistently high-quality healthcare is becoming increasingly difficult, and technology is not helping to make things easier.
Key Challenge:
- Increasingly complex and proprietary technologies
- Rapidly expanding body of medical knowledge
- Fragmented care processes with numerous handoffs
- Increasing patient and provider burden
Coordinated care systems are expensive to design, difficult to update, and hinder cross-organizational sharing. Since there is no standardized approach to workflow modeling, computer-interpretable guidelines have struggled to gain widespread adoption, leaving healthcare organizations to repeatedly solve the same problems in isolation.
BPM+ Approach
BPM+ uses widely supported modeling approaches to capture clinical best practices in a way that is computable, adaptable, shareable, and reusable.
BPM+ Differentiators:
- Clinical logic decoupled from proprietary code
- Rapidly updatable clinical logic
- Single source of truth to unify care delivery
- Facilitates automation & AI integration
BPM+ models capture the nuance, variability, and complex decision-making inherent in healthcare in a human-readable and computable model. They allow clinical logic to be managed independently from the technology that delivers it. As AI transforms healthcare, BPM+ provides a source of groundtruth for understanding opportunities and risks.
How does BPM+ capture healthcare delivery in action?
At its core, BPM+ is about capturing healthcare activities in a standardized format. BPM+ Community Ambassador Denis Gagne discusses how Business Process Modeling Notation (BPMN) provides the foundation of the BPM+ Approach.
How does BPM+ differ from other healthcare modeling approaches?
BPM+ utilizes a suite of OMG-standard modeling notations to accurately capture complex healthcare activities (hence the "+" in BPM+). Each notation captures a unique aspect of healthcare activities, allowing for robust representation of care pathways.
BPMN (Business Process Model and Notation)
BPMN is a graphical modeling standard used to represent structured, team-based workflows and processes. In healthcare, it helps model predictable clinical activities, task sequences, handoffs, and information flows in a way that is both human-readable and executable by technology systems.
CMMN (Case Management Model and Notation)
CMMN is used to model less predictable, event-driven, and adaptive clinical work where care providers must respond flexibly to changing conditions. It supports unstructured workflows, allowing clinicians to choose actions dynamically based on the evolving state of a patient or case.
DMN (Decision Model and Notation)
DMN is a standard for modeling and documenting clinical decisions using clear, understandable decision tables and logic models. It helps organizations represent complex decision-making rules in a format that clinicians, analysts, and software systems can all understand and apply consistently.
What are the advantages of adopting BPM+?
Shared Understanding
Flexibility
& Agility
Accessibility
& Reusability
The BPM+ allows clinical workflows, adaptive case management, and complex decision logic together in a unified environment. These detailed BPM+ models can be used to document requirements, objectively compare care pathways, guide EHR modernization, and drive software implementation.
Since BPM+ models are low-code/no-code, clinical decision and case-management logic can be easily updated. New clinical guidelines can be put into production in minutes rather than days or months.
BPM+ creates shareable, reusable, and platform-independent models that all clinical stakeholders can understand, built on internationally recognized OMG modeling standardswith broad tool support. This allows organizations to confidently adapt and implement best-in-class care pathways without having to build them from scratch.
How are shareable clinical pathways created with BPM+?
The BPM+ approach enables narrative guidelines to be accurately captured in a platform-independent model, facilitating their sharing and adoption across systems.