Formlet-Based Clinical Data Surfacing via SOA

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Healthcare entities face challenges in customizing clinical workflows due to system restrictions and lack of interoperability between different healthcare information systems, requiring manual requests to manufacturers and significant updates, which hinders efficient data management and patient care.

Innovation Solution

A clinical knowledge platform with a Service-Oriented Architecture (SOA) enables healthcare institutions to customize clinical workflows dynamically, aggregate data from disparate sources, and compare it against evidence-based best practices, using standardized vocabulary and intuitive user interfaces for real-time patient data access and comparison.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If healthcare information systems use standardized architectures and interfaces, then interoperability and ease of customization improve, but system complexity and implementation difficulty increase

Engineering Contradiction:
Improveworkflow customization capabilityVSAvoidsystem architecture complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system segments workflow customization into discrete, manageable components called formlets that can be independently selected, configured, and assembled. Each formlet represents a modular unit of clinical workflow functionality that can be customized without affecting the entire system, thereby improving adaptability while managing complexity through decomposition.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements a universal service-oriented architecture where a core platform provides standardized interfaces and services that support multiple clinical workflows and data sources. This universal foundation enables diverse customization needs to be met through configuration rather than code changes, improving versatility while maintaining architectural simplicity through reuse.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Loss of information

If detailed patient data is displayed to all users, then information completeness improves, but information overload and processing time increase

Engineering Contradiction:
Improvepatient data completenessVSAvoiddata processing time
Core Design Contradiction:
Loss of informationVSLoss of time

Solution Approach 1:

The system applies local quality by providing different levels of data detail to different users based on their roles, needs, and context. The formlet framework enables dynamic customization of data presentation, showing comprehensive details to users who need them while presenting summarized views to others, thereby maintaining information completeness where needed while reducing processing time where appropriate.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The patent implements dynamic data presentation where the level of detail displayed adapts based on user interactions, system context, and individual preferences. Users can dynamically adjust the granularity of patient data displayed through the formlet interface, allowing the system to optimize between information completeness and processing efficiency in real-time based on actual user needs.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS8887090B2Surfacing of detailed information via formlets
Publication Date: 2014.11.11 IHC HEALTH SERVICES INC
  • US8887090B2 patent drawing
  • US8887090B2 patent drawing
  • US8887090B2 patent drawing

AI summary

Certain examples provide systems, methods, apparatus, etc., to provide varying levels of detail in clinical data for one or more patients to a user. An example method to surface varying degrees of patient data via a formlet-based user interface includes providing a high-level view of data for one or more patients, the high-level view having a first level of detail. The example method includes generating, in response to a hover over a portion of the high-level view, a hover view providing a second level of detail of the data associated with the portion of the high-level view. The example method includes providing an inspector to access a third level of detail of the data. The example method includes generating a fourth level of detail in response to a trigger within the inspector.