Operating system

• US 8,689,008 B2
• Filed: 08/05/2009
• Issued: 04/01/2014
• Est. Priority Date: 08/05/2008
• Status: Active Grant

• Current Assignee: Allscripts Software LLC (Veradigm, Inc.)
• Original Assignee: Net.Orange Inc.
• Inventors: Rangadass, Vasu, Seshadri, Ravi
• Primary Examiner(s): Zecher, Cordelia
• Assistant Examiner(s): LAKHIA, VIRAL S
• Application Number:
  US12/536,060
• Publication Number:
  US 20100037067A1
• Time in Patent Office: 1,700 Days
• Field of Search: 713182-189, 713/193, 705/2, 705/3, 726/2, 726/27, 380/59
• US Class Current: 713/189
• CPC Class Codes: G06F 9/46 Multiprogramming arrangements

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.

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.

2. The clinical operating system according to claim 1 wherein the event management services modules comprises a routing services layer which provides services associated with processing of routing requests to service providers, including routing, logging, and monitoring of messages.

3. The clinical operating system according to claim 1 wherein the process management module comprises a configuration services layer having an extensible markup language based registry which stores data needed to support the system configuration.

4. The clinical operating system according to claim 1 wherein the services module comprises an application services layer which contains specific information necessary to meet implementation requirements for systems incorporated into the clinical operating system.

5. The clinical operating system according to claim 1 wherein the services module further comprises an operating system administration portal and a general administration portal, wherein the operating system administration portal comprises a reference implementation of a browser-based user interface which provides user access to web service interface.

6. The clinical operating system according to claim 1 wherein each service provides access to its data store by accepting typed messages routed thereto, utilizing a standard adapter that accepts, processes, and returns messages.

7. The clinical operating system according to claim 1 wherein the services module comprises a cOS administration portal and a general administration portal, wherein the cOS administration portal comprises a reference implementation of a browser-based user interface, which provides user access to a web service interface.

8. The clinical operating system according to claim 1 wherein the data services module comprises a data administration services layer having a set of data administration services which provide the ability to maintain data stored within each services.

9. The clinical operating system according to claim 1 wherein the security module comprises infrastructure services layers, the infrastructure services layers comprising a security envelope, exception management, logging and auditing services, and change management services.

10. The clinical operating system according to claim 1 wherein the governance module comprises infrastructure services layers, the infrastructure services layers comprising a security envelope, exception management, logging and auditing services, and change management services.

11. The clinical operating system according to claim 1 wherein a message generated by the operating system comprises a message header and a payload, the payload comprising a message body and an associated message type.

12. The clinical operating system according to claim 1 wherein the operating system connects with a clinical decision support system for providing a user of the operating system with best practices and updated clinical research and results information, the support system comprising a discovery repository, a clinical discovery logic manager module, a vocabulary repository, and an event sub-system repository.

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.

14. The clinical operating system according to claim 13 further comprising a plurality of plug-ins.

15. The clinical operating system according to claim 13 further comprising a clinical file system for patient records, the file system comprising an encrypted protective shell;

metadata;

a yolk; and

a self-contained clinical file executable comprising relevant content;

associated access rules, and a challenge mechanism to read and write content and a self-destructing scheme after an expiry period.

16. The clinical operating system according to claim 13 wherein the virtual data layer and discovery module comprises a federated search engine leveraging metadata from semantic information sources to disambiguate search queries to provide relevant results;

a clustering mechanism partitioning data into subsets that share common traits;

a user query invoking plug-in actions and crawler actions;

wherein the relevant results are thereafter filtered and clustered and thereafter displayed by a visualization operation.

17. The clinical operating system according to claim 13 wherein the security module comprises infrastructure services layers, the infrastructure services layers comprising a security envelope, exception management, logging and auditing services, and change management services.

18. The clinical operating system according to claim 13 wherein the governance module comprises infrastructure services layers, the infrastructure services layers comprising a security envelope, exception management, logging and auditing services, and change management services.

19. The clinical operating system according to claim 13 wherein a message generated by the operating system comprises a message header and a payload, the payload comprising a message body and an associated message type.

20. The clinical operating system according to claim 13 wherein the operating system connects with a clinical decision support system for providing a user of the operating system with best practices and updated clinical research and results information, the support system comprising a discovery repository, a clinical discovery logic manager module, a vocabulary repository, and an event sub-system repository.