Architecture for a content driven clinical information system
Certain examples provide systems, methods, and apparatus for a content-based clinical information system. An example system includes a reference platform to define and provide core system capabilities and to interpret and execute content items while remaining application neutral. The example system includes a plurality of content items authored independent of the reference platform to define clinical functionality for one or more content-based clinical applications by leveraging the reference platform. In the example system, the plurality of content items is to be created and deployed independently of the creation and deployment of the one or more content-based clinical applications. The plurality of content items is to remain independent of the implementation of the reference platform to allow independent evolution of the platform and the one or more content-based clinical applications.
1. A healthcare computer system comprising:
a processor organized to provide platform services to a plurality of distinct clinical applications by forming at least:
a content storage service to store content items representing clinical application functionality, the content items organized in a hierarchy according to context variant, each context variant based at least in part on a distinct user clinical role and representing at least one of a distinct configuration or preference for depicting, on an electronic display, the clinical application functionality associated with the respective content item;
a content directory service to index the stored content items for query, retrieval, and organization with respect to the plurality of distinct clinical applications;
a content packaging service to package one or more stored content items for deployment to and use by each of the plurality of distinct clinical applications based on a context value and a dependency graph;
a content lifecycle service including at least one state machine to monitor and manage the one or more content items through transitions between two or more associated states with respect to the plurality of distinct clinical applications according to a system workflow corresponding to the respective states in the state machine; and
a content manager structured to electronically communicate with the content storage service, the content directory service, the content packaging service, and the content lifecycle service to coordinate the content storage service, the content directory service, the content packaging service, and the content lifecycle service to provide a reference platform on which to construct, deploy, and execute each of the plurality of distinct clinical applications;
wherein:
each content item includes:
a) a root content item represented by an identifier; and
b) one or more context variants that represent variations of an implementation of the content item in different contexts organized as children of the root content item; and
the platform services include:
a) reference platform services to implement content class managers;
b) content class managers to implement management services for one or more content classes; and
c) content class interpreters to consume a content item and execute instructions defined in the content item for a content class, wherein each of the plurality of distinct clinical applications is composed of content items managed by the content class managers and executed by the content class interpreters.
2. The system of claim 1 , wherein the context variants form trees of increasing context specialization.
3. The system of claim 1 , wherein each context variant is associated with an identifier and maintains a version history of the respective context variant including changes applied thereto.
4. The system of claim 1 , wherein a first context variant to be packaged by the content packaging service for a first distinct clinical application, of the plurality, is to be deployed as a content frame with terminology dependencies inferred and resolved at runtime using terminology relationships and mapping.
5. The system of claim 1 , wherein the dependency graph identifies dependencies between content items.
6. The system of claim 1 , wherein each content item is identified by a uniform resource indicator and associated with metadata, and wherein the metadata is searchable to obtain the uniform resource indicator to retrieve the respective content item.
7. The system of claim 1 , wherein the one or more content items are to be deployed as clinical element type objects with an extensible markup language schema.
8. The system of claim 1 , wherein the each of the plurality of distinct clinical applications is to interpret the content items using the platform services to execute the clinical application functionality associated with the content items.
9. At least one non-transitory computer-readable storage medium including instructions that, when executed, cause at least one processor to provide platform services to a plurality of distinct clinical applications by implementing at least:
a content storage service to store content items representing clinical application functionality, the content items organized in a hierarchy according to context variant, each context variant based at least in part on a distinct user clinical role and representing at least one of a distinct configuration or preference for depicting, on an electronic display, the clinical application functionality associated with the respective content item;
a content directory service to index the stored content items for query, retrieval, and organization with respect to the plurality of distinct clinical applications;
a content packaging service to package one or more stored content items for deployment to and use by each of the plurality of distinct clinical applications based on a context value and a dependency graph;
a content lifecycle service including at least one state machine to monitor and manage the one or more content items through transitions between two or more associated states with respect to the plurality of distinct clinical applications according to a system workflow corresponding to the respective states in the state machine; and
a content manager structured to electronically communicate with the content storage service, the content directory service, the content packaging service, and the content lifecycle service to coordinate the content storage service, the content directory service, the content packaging service, and the content lifecycle service to provide a reference platform on which to construct, deploy, and execute each of the plurality of distinct clinical applications;
wherein:
each content item includes:
a) a root content item represented by an identifier; and
b) one or more context variants that represent variations of an implementation of the content item in different contexts organized as children of the root content item; and
the platform services include:
a) reference platform services to implement content class managers;
b) content class managers to implement management services for one or more content classes; and
c) content class interpreters to consume a content item and execute instructions defined in the content item for a content class, wherein each of the plurality of distinct clinical applications is composed of content items managed by the content class managers and executed by the content class interpreters.
10. The at least one non-transitory computer-readable storage medium of claim 9 , wherein the context variants form trees of increasing context specialization.
11. The at least one non-transitory computer-readable storage medium of claim 9 , wherein each context variant is associated with an identifier and maintains a version history of the respective context variant including changes applied thereto.
12. The at least non-transitory one computer-readable storage medium of claim 9 , wherein a first context variant to be packaged by the content packaging service for a first distinct clinical application, of the plurality, is to be deployed as a content frame with terminology dependencies inferred and resolved at runtime using terminology relationships and mapping.
13. The at least one non-transitory computer-readable storage medium of claim 9 , wherein the dependency graph identifies dependencies between content items.
14. The at least one non-transitory computer-readable storage medium of claim 9 , wherein each content item is identified by a uniform resource indicator and associated with metadata, and wherein the metadata is searchable to obtain the uniform resource indicator to retrieve the respective content item.
15. The at least one non-transitory computer-readable storage medium of claim 9 , wherein the one or more content items are to be deployed as clinical element type objects with an extensible markup language schema.
16. The at least one non-transitory computer-readable storage medium of claim 9 , wherein each of the plurality of distinct clinical applications is to interpret the content items using the platform services to execute the clinical application functionality associated with the content items.