Clinical content-driven architecture systems and methods of use

• US 9,911,167 B2
• Filed: 02/21/2012
• Issued: 03/06/2018
• Est. Priority Date: 02/21/2011
• Status: Active Grant

• Current Assignee: General Electric Company
• Original Assignee: General Electric Company
• Inventors: James, Alan Ferris, Agrawal, Nitin
• Primary Examiner(s): Paulson, Sheetal R
• Application Number:
  US13/401,057
• Publication Number:
  US 20120215562A1
• Time in Patent Office: 2,205 Days
• Field of Search: 705 2- 3
• CPC Class Codes: G06Q 50/22 Social work or social welfare, e.g. community support activities or counselling services
• CPC Class Codes: G16H 10/20 for electronic clinical trials or questionnaires
• CPC Class Codes: G16H 10/60 for patient-specific data, e.g. for electronic patient records
• CPC Class Codes: G16H 30/20 for handling medical images, e.g. DICOM, HL7 or PACS
• CPC Class Codes: G16H 40/20 for the management or administration of healthcare resources or facilities, e.g. managing hospital staff or surgery rooms
• CPC Class Codes: G16H 70/00 ICT specially adapted for the handling or processing of medical references
• CPC Class Codes: G16Z 99/00 Subject matter not provided for in other main groups of this subclass

Abstract

Certain examples provide methods, systems and apparatus of content-driven clinical information management. An example method includes facilitating authoring of content and combination of the content into a content-based application, wherein content represents a parameterization of instructions to instruct the content-based application how to operate, the content formulated according to one or more detailed clinical models. The example method includes packaging and deploying the content-based application using a processor to one or more targets for installation. The example method includes facilitating installation of the packaged content-based application at the one or more targets. The example method includes managing the content-based application remotely from the one or more targets. In the example method, content is to be created, stored, deployed, and retrieved independently of the creation and deployment of the content-based application consuming data based on the content.

Claims

1. A method of content-driven clinical information management comprising:

facilitating, using a first processor and an interface at a first computer system, authoring of content and combination of a plurality of the content to form a content-based application, the content representing a parameterization of instructions executable to instruct the content-based application regarding how the application is to operate in conjunction with received data, the received data being distinct from the content forming the content-based application, the content organized into one or more formlets to form the content-based application according to one or more detailed clinical models, the detailed clinical models specifying content structure, content interconnection and content behavior according to a formlet definition to form the content-based application, the detailed clinical models specifying treatment of the received data by the content,

wherein facilitating authoring of content and combination of a plurality of the content to form a content-based application further includes (i) automatically selecting, by the processor, a context variant of a content item from among a plurality of available context variants arranged in a context hierarchy stored in content storage for the content item based on a comparison of an input context value to the plurality of available context variants to automatically reject conflicting context variants and more specific context variants to select a most specific context variant of remaining available context variants as a selected context variant and (ii) using, by the processor, the selected context variant of the content item retrieved from the context hierarchy stored in the content storage in forming the content-based clinical application, the selected context variant associated with an identifier and a relationship to the content item;

packaging and deploying the content based application, using the processor and based at least part on the identifier and relationship of the selected context variant, to at least a second computer system at one or more target sites for installation;

facilitating, using the processor, installation of the packaged content based application at the one or more target sites; and

managing, using the processor, an update for the content based application remotely from the one or more target sites,

wherein content is created, stored, deployed, and retrieved independently of the creation and deployment of the content-based application, the content-based application to consume data and execute the content with respect to the received data and a reference platform, and wherein the reference platform alters a second processor to form a clinical information system including a content class manager to form the content item and its parameterized instructions into a content frame according to the selected context variant to form the content-based application, and the content-based application is executed via a content class interpreter to configure the second processor to interpret the content forming the content-based application using the reference platform.

2. The method of claim 1, wherein the content-based application is versioned for each of a plurality of target sites.

3. The method of claim 2, further comprising tracking the versioned content-based application for compatibility among versions.

4. The method of claim 1, wherein the content includes structured and unstructured clinical content.

5. The method of claim 1, wherein facilitating further comprises facilitating authoring of a scalable content-based application for a clinical enterprise.

6. The method of claim 1, wherein content comprises at least one of configuration content, preferences content, reference content, and application content.

7. The method of claim 1, wherein content is structured to facilitate semantic interoperability.

8. The method of claim 1, wherein facilitating authorizing of content further comprises automatically identifying, using a processor, dependencies, tasks, and associated resources to form the content-based application.

9. The method of claim 1, wherein content includes data read and interpreted by the content-based clinical application to at least one of define and modify at least one of presentation, behavior, and semantics of at least one of the content-based clinical application and data consumed by the content-based clinical application.

10. A tangible computer-readable storage device including computer program code which, when executed, implements a method of content-driven clinical information management, the method comprising:

facilitating, using a first processor and an interface at a first computer system, authoring of content and combination of a plurality of the content to form a content-based application, the content representing a parameterization of instructions executable to instruct the content-based application regarding how the application is to operate in conjunction with received data, the received data being distinct from the content forming the content-based application, the content organized into one or more formlets to form the content-based application according to one or more detailed clinical models, the detailed clinical models specifying content structure, content interconnection and content behavior according to a formlet definition to form the content-based application, the detailed clinical models specifying treatment of the received data by the content,

wherein facilitating authoring of content and combination of a plurality of the content to form a content-based application further includes (i) automatically selecting, by the processor, a context variant of a content item from among a plurality of available context variants arranged in a context hierarchy stored in content storage for the content item based on a comparison of an input context value to the plurality of available context variants to automatically reject conflicting context variants and more specific context variants to select a most specific context variant of remaining available context variants as a selected context variant and (ii) using, by the processor, the selected context variant of the content item retrieved from the context hierarchy stored in the content storage in forming the content-based clinical application, the selected context variant associated with an identifier and a relationship to the content item;

packaging and deploying the content based application, using the processor and based at least part on the identifier and relationship of the selected context variant, to at least a second computer system at one or more target sites for installation;

facilitating, using the processor, installation of the packaged content based application at the one or more target sites; and

managing, using the processor, an update for the content based application remotely from the one or more target sites,

wherein content is created, stored, deployed, and retrieved independently of the creation and deployment of the content-based application, the content-based application to consume data and execute the content with respect to the received data and a reference platform, and wherein the reference platform alters a second processor to form a clinical information system including a content class manager to form the content item and its parameterized instructions into a content frame according to the selected context variant to form the content-based application, and the content-based application is executed via a content class interpreter to configure the second processor to interpret the content forming the content-based application using the reference platform.

11. The computer-readable storage device of claim 10, wherein the content-based application is versioned for each of a plurality of target sites.

12. The computer-readable storage device of claim 11, wherein the method further comprises tracking the versioned content-based application for compatibility among versions.

13. The computer-readable storage device of claim 10, wherein the content includes structured and unstructured clinical content.

14. The computer-readable storage device of claim 10, wherein facilitating further comprises facilitating authoring of a scalable content-based application for a clinical enterprise.

15. The computer-readable storage device of claim 10, wherein content comprises at least one of configuration content, preferences content, reference content, and application content.

16. The computer-readable storage device of claim 10, wherein content is structured to facilitate semantic interoperability.

17. The computer-readable storage device of claim 10, wherein facilitating authorizing of content further comprises automatically identifying, using a processor, dependencies, tasks, and associated resources to form the content-based application.

18. The computer-readable storage device of claim 10, wherein content includes data read and interpreted by the content-based clinical application to at least one of define and modify at least one of presentation, behavior, and semantics of at least one of the content-based clinical application and data consumed by the content-based clinical application.