EHR Specialty Views for Role-Based Clinical Domain Ordering
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current graphical user interface methodologies for electronic healthcare records (EHR) applications do not cater to the varying clinical interests of healthcare practitioners, requiring them to scroll through menus to access relevant domains, which is inefficient.
Innovation Solution
Implementing specialty views in EHR applications that determine a user's role and prioritize clinical domains and vocabularies based on configuration information, allowing for customized ordering and display of clinical data, thereby providing a tailored interface for each practitioner's specialty.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of manufacture
If a standardized EHR interface with fixed domain ordering is used, then system consistency and ease of implementation are improved, but accessibility of relevant clinical domains for specialty practitioners deteriorates
Solution Approach 1:
The interface dynamically reorders clinical domains based on the practitioner's specialty role. When a practitioner logs in, the system retrieves their role information and automatically arranges the domain menu to prioritize specialties relevant to that role, transforming a static interface into an adaptive one that responds to user characteristics.
Solution Approach 2:
The interface applies different ordering configurations to different practitioner roles. Each specialty (e.g., cardiology, oncology, pediatrics) receives a customized domain arrangement tailored to their specific clinical needs, allowing each local user group to access their most frequently used domains in prominent positions.
2Loss of information
If all clinical domains are displayed in a fixed menu order, then completeness of information is improved, but time to access relevant domains deteriorates
Solution Approach 1:
The system pre-configures domain orderings for each practitioner role before the practitioner needs to access them. During login, the system retrieves the appropriate pre-defined ordering from configuration files or databases, so that when the practitioner views the interface, the domains are already optimally arranged without requiring real-time computation or manual adjustment.
3Productivity
If a role-based customized interface is implemented, then productivity of practitioners is improved, but system complexity deteriorates
Solution Approach 1:
The system changes the ordering parameter of the domain menu based on the practitioner's role. Instead of redesigning the entire interface architecture, it modifies a single key parameter (domain sequence) according to role-based configuration data, allowing customization with minimal impact on overall system structure.
Data Source
AI summary
A medical software application is configurable to allow different specialty views to be specified for healthcare practitioners having different characteristics (e.g. specialists in different fields), based on, for example, role or specialty information for a logged in user. A specialty view is further be configured to affect the display of data within a domain. A specialty view can specify that a certain vocabulary takes priority for display purposes (e.g. display ordering).