Operating system
First Claim
Patent Images
1. A clinical operating system architecture implemented on a web server comprising:
- an event management services module;
a process management module connected with the event management module;
a services module connected with the process management module, wherein the services module handles security needs for all application services, wherein the application services comprise patient services, practitioner services and clinical event services, wherein the patient services provide authoritative patient identifiers and corresponding basic demographic information within the operating system, wherein the practitioner services provide authoritative identifiers of healthcare providers and corresponding basic demographic information within the operating system, wherein the clinical event services provide an authoritative index of clinical event information available within a context of the operating system;
a data services module connected with the services module;
a data federation module connected with the data services module;
a security module; and
a governance module;
wherein each module comprises self-contained service layers coupled together and all modules are interconnected and communicate therebetween;
wherein the data federation module inputs into an operating system database through a schema based invocation framework such that the operating system is configured to extract data from proprietary and external systems and translate the data for universal access, wherein the data federation module includes adaptors that read the data and translate the data, wherein the data is converted to one or more messages, wherein each message comprises a payload and a header in an XML-based document structure, wherein the translating the data includes applying transformation rules to metadata using a checklist, wherein the data federation module maps data elements to relational schema tables and abstracts users from underlying data provider details, wherein the data federation module communicates with down-stream data sources using a variety of protocols, wherein the data sources include applications, databases, services and hardware;
wherein an external database inputs into the data federation module through an external services module; and
wherein the security module encrypts utilizing a PKI standard and wherein the governance module gets policy requirements from a policy database.
6 Assignments
0 Petitions
Accused Products
Abstract
A new and improved operating system comprising a series of self-contained interconnected modules and service layers for connecting proprietary systems together and extracting and translating data therefrom enables existing software systems to operate and cooperate in an existing software ecosystem while allowing flexible connections with both existing and new applications.
-
Citations
20 Claims
-
1. A clinical operating system architecture implemented on a web server comprising:
-
an event management services module; a process management module connected with the event management module; a services module connected with the process management module, wherein the services module handles security needs for all application services, wherein the application services comprise patient services, practitioner services and clinical event services, wherein the patient services provide authoritative patient identifiers and corresponding basic demographic information within the operating system, wherein the practitioner services provide authoritative identifiers of healthcare providers and corresponding basic demographic information within the operating system, wherein the clinical event services provide an authoritative index of clinical event information available within a context of the operating system; a data services module connected with the services module; a data federation module connected with the data services module; a security module; and a governance module; wherein each module comprises self-contained service layers coupled together and all modules are interconnected and communicate therebetween; wherein the data federation module inputs into an operating system database through a schema based invocation framework such that the operating system is configured to extract data from proprietary and external systems and translate the data for universal access, wherein the data federation module includes adaptors that read the data and translate the data, wherein the data is converted to one or more messages, wherein each message comprises a payload and a header in an XML-based document structure, wherein the translating the data includes applying transformation rules to metadata using a checklist, wherein the data federation module maps data elements to relational schema tables and abstracts users from underlying data provider details, wherein the data federation module communicates with down-stream data sources using a variety of protocols, wherein the data sources include applications, databases, services and hardware; wherein an external database inputs into the data federation module through an external services module; and wherein the security module encrypts utilizing a PKI standard and wherein the governance module gets policy requirements from a policy database. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12)
-
-
13. A clinical operating system architecture implemented on a web server comprising:
-
a services module connected with a process management module, wherein the services module handles security needs for all application services, wherein the application services comprise patient services, practitioner services and clinical event services, wherein the patient services provide authoritative patient identifiers and corresponding basic demographic information within the operating system, wherein the practitioner services provide authoritative identifiers of healthcare providers and corresponding basic demographic information within the operating system, wherein the clinical event services provide an authoritative index of clinical event information available within a context of the operating system; a monitoring and routing module; an operating system workflow module connected with the monitoring and routing module; a message organ module connected with the operating system workflow module; an external data layer module connected with the message organ module; a virtual data layer and discovery module which inputs into an operating system data database, the virtual data layer and discovery module connected with the external data layer; wherein each module comprises self-contained service layers coupled together and all modules are interconnected and communicate therebetween; wherein the virtual data layer abstracts data from up-stream consumers through a schema based invocation framework such that the operating system is configured to extract data from proprietary and external systems and translate the data for universal access, wherein the virtual data layer facilitates reading the data and translating the data, wherein the data is converted to one or more messages, wherein each message comprises a payload and a header in an XML-based document structure, wherein the translating the data includes applying transformation rules to metadata using a checklist, wherein the virtual data layer maps data elements to relational schema tables and abstracts users from underlying data provider details, wherein the virtual data layer communicates with down-stream data sources using a variety of protocols, wherein the data sources include applications, databases, services and hardware; wherein an external database inputs into the virtual data layer and discovery module through an external services module; and wherein the security module encrypts utilizing a PKI standard and wherein the governance module gets policy requirements from a policy database. - View Dependent Claims (14, 15, 16, 17, 18, 19, 20)
-
Specification