System and method to develop health-care information systems
First Claim
Patent Images
1. A system for developing health care business applications, comprising:
- a server coupled to a data repository;
a software system executing on the server from a non-transitory machine-readable physical medium, the software system comprising;
a foundation services tier (FST) providing modules with operating system functionalities including resource allocation and a scheduling function, and modules with middleware functionalities including messaging and knowledge integration, wherein all tasks that are scheduled are initiated through the scheduler function, with each defined task comprising constraints, and if the constraints cannot be satisfied within a current context, the scheduler notifies a task initiator with a precise indication of the reasons, providing Quality of Service (QoS) guarantees, and wherein user'"'"'s security authorizations are managed by a Globally-Controlled Locally Managed (GCLM) system in which users are grouped into non-overlapping security domains, each managed by a security domain administrator (SDA), and users are assigned privileges defined by application designers at a lowest level of granularity;
a domain services tier (DST) comprising a workflow software (SW) engine having specific process states, and thus having state transitions, triggered by events, all defined by an XML-based configuration mechanism of the workflow software engine, and Application Programming Interfaces (APIs) for developing the healthcare business process applications, wherein each call to an API is routed to a Quality of Service (QoS) subsystem before being executed, and QoS standards are enforced in operation of the API and any healthcare business process application implemented through the API, and wherein the healthcare business process applications are developed for a specific healthcare enterprise, and after development are deployed to be executed at the specific enterprise by users who are associated with and granted privileges for that enterprise; and
an application services tier (AST) comprising specific healthcare business process applications developed using the workflow software engine and APIs of the DST, the healthcare business process applications implemented using services of the workflow software engine and communicating with one another in the AST using a publish-subscribe model provided by a subscription manager, in which messages are published by individual applications without being addressed to any specific destination, and applications subscribe according to interest without regard to any specific source, and wherein in the AST all entered data is routed through a health care standards subsystem before being accepted as clinical data, thus ensuring standards compliance.
2 Assignments
0 Petitions
Accused Products
Abstract
A method of and a system for development of health care information Systems (HIS) are disclosed. The method includes providing software programming interfaces for development of application modules, communication interfaces for establishing communication between various modules, and resource management interfaces for allocation of resources such as memory. The system comprises of a server with a health care middleware operating system (HMOS). The HMOS is designed as a multi-tier architecture with 3 tiers namely, application tier, domain services tier, and Foundations tier.
-
Citations
5 Claims
-
1. A system for developing health care business applications, comprising:
-
a server coupled to a data repository; a software system executing on the server from a non-transitory machine-readable physical medium, the software system comprising; a foundation services tier (FST) providing modules with operating system functionalities including resource allocation and a scheduling function, and modules with middleware functionalities including messaging and knowledge integration, wherein all tasks that are scheduled are initiated through the scheduler function, with each defined task comprising constraints, and if the constraints cannot be satisfied within a current context, the scheduler notifies a task initiator with a precise indication of the reasons, providing Quality of Service (QoS) guarantees, and wherein user'"'"'s security authorizations are managed by a Globally-Controlled Locally Managed (GCLM) system in which users are grouped into non-overlapping security domains, each managed by a security domain administrator (SDA), and users are assigned privileges defined by application designers at a lowest level of granularity; a domain services tier (DST) comprising a workflow software (SW) engine having specific process states, and thus having state transitions, triggered by events, all defined by an XML-based configuration mechanism of the workflow software engine, and Application Programming Interfaces (APIs) for developing the healthcare business process applications, wherein each call to an API is routed to a Quality of Service (QoS) subsystem before being executed, and QoS standards are enforced in operation of the API and any healthcare business process application implemented through the API, and wherein the healthcare business process applications are developed for a specific healthcare enterprise, and after development are deployed to be executed at the specific enterprise by users who are associated with and granted privileges for that enterprise; and an application services tier (AST) comprising specific healthcare business process applications developed using the workflow software engine and APIs of the DST, the healthcare business process applications implemented using services of the workflow software engine and communicating with one another in the AST using a publish-subscribe model provided by a subscription manager, in which messages are published by individual applications without being addressed to any specific destination, and applications subscribe according to interest without regard to any specific source, and wherein in the AST all entered data is routed through a health care standards subsystem before being accepted as clinical data, thus ensuring standards compliance. - View Dependent Claims (2, 3, 4, 5)
-
Specification