System and method for configuring clinical workflows and generating user interfaces thereof
First Claim
1. A computer-implemented method for defining clinical workflows, via program instructions stored in a memory and executed by a processor, the computer-implemented method comprising:
- receiving, at a server-end, information related to one or more clinical workflows;
translating the received information into a machine readable language, wherein the received information is translated by splitting the received information into one or more structural components and translating each of the one or more structural components;
storing the translated information as metadata, wherein the step of storing the translated information as the metadata comprises storing the translated information for each of the one or more structural components and their association with other structural components as the metadata, wherein the metadata comprises one or more flags to control one or more predefined values corresponding to one or more patient parameters such that flags facilitate triggering of one or more clinical workflows, on one or more client devices, when the one or more predefined values match with values of the one or more patient parameters received at the one or more client devices; and
synchronizing the stored metadata with one or more client devices, communicatively coupled to the server-end, to define the one or more clinical workflows in the one or more client devices, wherein the one or more defined clinical workflows are dynamically customized based on one or more patient parameters, further wherein synchronization facilitates defining and customization of the one or more clinical workflows on the one or more client devices when the one or more client devices are not connected with the server-end.
1 Assignment
0 Petitions
Accused Products
Abstract
A computer-implemented method, system and computer program product for defining clinical workflows is provided. The computer-implemented comprises receiving, at a server-end, information related to one or more clinical workflows. The computer-implemented method further comprises translating the received information into a machine readable language, wherein the received information is translated by splitting the received information into one or more structural components and translating each of the one or more structural components. Furthermore, the computer-implemented method comprises storing the translated information as metadata. Also, the computer-implemented method comprises synchronizing the stored metadata with one or more client devices to define the one or more clinical workflows in the one or more client devices, wherein the one or more defined clinical workflows are dynamically customized based on one or more patient parameters.
-
Citations
16 Claims
-
1. A computer-implemented method for defining clinical workflows, via program instructions stored in a memory and executed by a processor, the computer-implemented method comprising:
-
receiving, at a server-end, information related to one or more clinical workflows; translating the received information into a machine readable language, wherein the received information is translated by splitting the received information into one or more structural components and translating each of the one or more structural components; storing the translated information as metadata, wherein the step of storing the translated information as the metadata comprises storing the translated information for each of the one or more structural components and their association with other structural components as the metadata, wherein the metadata comprises one or more flags to control one or more predefined values corresponding to one or more patient parameters such that flags facilitate triggering of one or more clinical workflows, on one or more client devices, when the one or more predefined values match with values of the one or more patient parameters received at the one or more client devices; and synchronizing the stored metadata with one or more client devices, communicatively coupled to the server-end, to define the one or more clinical workflows in the one or more client devices, wherein the one or more defined clinical workflows are dynamically customized based on one or more patient parameters, further wherein synchronization facilitates defining and customization of the one or more clinical workflows on the one or more client devices when the one or more client devices are not connected with the server-end. - View Dependent Claims (2, 3, 4, 5, 6, 7)
-
-
8. A system for defining clinical workflows, the system comprising:
-
a user interface, at a server-end, configured to receive information related to one or more clinical workflows; an interpreter configured to translate the received information into a machine readable language, wherein the received information is translated by splitting the received information into one or more structural components and translating each of the one or more structural components; a metadata convertor configured to store the translated information as metadata in a server metadata repository, wherein storing the translated information as the metadata comprises storing the translated information for each of the one or more structural components and their association with other structural components as the metadata, wherein the metadata comprises one or more flags to control one or more predefined values corresponding to one or more patient parameters such that flags facilitate triggering of one or more clinical workflows, on one or more client devices, when the one or more predefined values match with values of the one or more patient parameters received at the one or more client devices; and a workflow configuration engine configured to synchronize the stored metadata with one or more client devices, communicatively coupled to the server-end, to define one or more clinical workflows in the one or more client devices, wherein the one or more defined workflows are dynamically customized based on one or more patient parameters, further wherein the synchronization facilitates defining and customization of the one or more clinical workflows on the one or more client devices when the one or more client devices are not connected with the server-end. - View Dependent Claims (9, 10, 11, 12, 13, 14)
-
-
15. A computer program product for defining clinical workflows, the computer program product comprising:
-
a non-transitory computer-readable medium having computer-readable program code stored thereon, the computer-readable program code comprising instructions that when executed by a processor, cause the processor to; receive, at a server-end, information related to one or more clinical workflows; translate the received information into a machine readable language, wherein the received information is translated by splitting the received information into one or more structural components and translating each of the one or more structural components; store the translated information as metadata, wherein the step of storing the translated information as the metadata comprises storing the translated information for each of the one or more structural components and their association with other structural components as the metadata, wherein the metadata comprises one or more flags to control one or more predefined values corresponding to one or more patient parameters such that flags facilitate triggering of one or more clinical workflows, on one or more client devices, when the one or more predefined values match with values of the one or more patient parameters received at the one or more client devices; and synchronize the stored metadata with one or more client devices, communicatively coupled to the server-end, to define the one or more clinical workflows in the one or more client devices, wherein the one or more defined clinical workflows are dynamically customized based on one or more patient parameters, further wherein synchronizing facilitates defining and customization of the one or more clinical workflows, at the one or more client devices, when the one or more client devices are not connected with the server-end. - View Dependent Claims (16)
-
Specification