OPERATING SYSTEM
A new and improved operating system is described. The system enables a user to receive information in many different types of formats and converts them into a uniform format. The system can also use the information to fill out forms in different types of formats, and then send them to the appropriate recipient.
1 . A clinical operating system server comprising:
a memory storing a plurality of executable self-contained service modules, including a services module comprising at least one consent services layer; and
a processor coupled with the memory and configured, by executing the at least one consent services layer, to:
accept a markup language message from a device via a message adapter within the services module;
provide, via at least one consent services layer, access to a portion of a patient's health record data within the at least one services module according to role-based privacy constraints based on the markup language message; and
return a return message, via the message adapter, relating to the portion of the patient's health record data.
2 . The server of claim 1 , wherein the role-based privacy constraints comprises HIPAA required constraints.
3 . The server of claim 1 , wherein the markup language message comprises a message header.
4 . The server of claim 3 , wherein the message header includes at least one of the following: a unique message identifier, a message type, a message status, and a message description.
5 . The server of claim 3 , wherein the message header lacks encryption.
6 . The server of claim 1 , wherein the markup language message comprises a message payload.
7 . The server of claim 6 , wherein the message payload comprises a message type.
8 . The server of claim 7 , wherein the message payload adheres to a schema defined for the message type.
9 . The server of claim 7 , wherein the message type is registered with the at least one consent services layer.
10 . The server of claim 6 , wherein the message payload is encrypted.
11 . The server of claim 1 , wherein the markup language message comprises data relevant to a patient treatment.
12 . The server of claim 11 , wherein the portion of the patient's health record data is less than the patient's entire health record.
13 . The server of claim 1 , wherein the return message includes the portion of the patient's health record data.
14 . The server of claim 1 , wherein the markup language message comprises a typed message.
15 . The server of claim 1 , wherein the markup language message adheres to an extensible markup language.
16 . The server of claim 1 , wherein the processor is further configured, by executing the at least one consent services layer, to return the return message to a second adapter.
17 . The server of claim 16 , wherein the second adapter is associated with at least one service module from the plurality of executable self-contained service modules.
18 . The server of claim 17 , wherein the at least one service module is selected from a group consisting of: an event management module, an event monitoring module, a process management module, a workflow module, a data services module, and a data federation module.
19 . The server of claim 16 , wherein the second adapter is associated with at least one services layer within the services module.
20 . The server of claim 19 , wherein the at least one service layer is selected from a group consisting of: a routing service layer, a configuration service layer, an application service layer, a clinical operating system administration portal, an infrastructure service layer, and a message management layer
21 . The server of claim 16 , wherein the second adapter comprises a device driver.
22 . The server of claim 1 , wherein the consent services layer is an application services layer within the services module.
23 . The server of claim 1 , wherein the adapter comprises a web server.
24 . The server of claim 23 , wherein the adapter further comprises a web service.
25 . The server of claim 1 , wherein each self-contained services module in the plurality of self-contained services modules loosely couples with other services modules via its own web services.
26 . The server of claim 1 , wherein the device comprises a portable device.