Skip to content

Commit 4613070

Browse files
authored
Merge pull request #362 from ipbabble/modularize-edd
Modularize edd
2 parents d26b3ce + 82b33ef commit 4613070

File tree

7 files changed

+138
-110
lines changed

7 files changed

+138
-110
lines changed

content/patterns/emerging-disease-detection/_index.adoc

Lines changed: 10 additions & 94 deletions
Original file line numberDiff line numberDiff line change
@@ -13,109 +13,25 @@ industries:
1313
aliases: /emerging-disease-detection/
1414
// pattern_logo: emerging-disease-detection.png
1515
links:
16-
install: getting-started
16+
install: edd-getting-started
1717
arch: https://www.redhat.com/architect/portfolio/architecturedetail?ppid=6
1818
help: https://groups.google.com/g/validatedpatterns
1919
bugs: https://github.com/validatedpatterns/emerging-disease-detection/issues
2020
ci: edd
21+
contributor:
22+
name: Arunkumar Nattamai Hariharan
23+
contact: mailto:anattama@redhat.com
24+
git: https://github.com/arunhari82
2125
---
22-
2326
:toc:
2427
:imagesdir: /images
2528
:_content-type: ASSEMBLY
26-
include::modules/comm-attributes.adoc[]:
27-
28-
== Background
29-
30-
Use case::
31-
32-
* Use a AI automation at the edge to detect emerging diseases.
33-
* Use an event driven architecture
34-
* Securely manage secrets across the deployment.
35-
+
36-
[NOTE]
37-
====
38-
Based on the requirements of a specific implementation, certain details might differ. However, all validated patterns that are based on a portfolio architecture, generalize one or more successful deployments of a use case.
39-
====
40-
41-
Background::
42-
No technology is better poised to transform Healthcare as AI and Business Process Automation. Coupled with an Edge Architecture, these continuous monitoring and detection systems can scale to provide early warning intervention and measurable process improvements, anywhere.
43-
44-
Detection of disease states like sepsis, stroke, pulmonary embolism, and heart attack requires low-latency, broadband, asynchronous streaming capabilities. We have prototyped an early warning platform built with a distributed edge architecture, fed by at-home post-operative monitoring (fitbit, smart phone, wifi devices) and automated Clinical care escalation and coordination processes. This platform has the potential to significantly lower network traffic and cost while providing early warning interventions for our nation's Veterans.
45-
46-
[id="about-solution"]
47-
== About the solution
48-
49-
To demonstrate the effectiveness of the solution this pattern focuses on the specific problem of Sepsis. Sepsis is the body's extreme response to an infection. It is a life-threatening medical emergency. Sepsis is a costly and life threatening condition that can result in multi-organ failure. Beating conditions like sepsis requires rapid detection and mitigation of risks. With the immune system compromised, recovery at home is often preferred to minimize the risk for cross-infections, yet medical teams often lack the capability to perform constant surveillance for emerging risks across their patient cohorts, especially in rural settings. In this session, we will demonstrate an early warning system driven by Clinical AI at the Edge, fed by at-home post-operative monitoring and automated Clinical care escalation and coordination processes.
50-
51-
== Technology Highlights:
52-
* Event-Driven Architecture
53-
* Data Science on OpenShift
54-
* Process Automation
55-
56-
== Solution Discussion and Demonstration
57-
In this demonstration, we will follow a vulnerable, post-operative patient, Alani, as she recovers from surgery in her home setting. The pattern demonstrates an early warning system driven by Clinical AI at the Edge, fed by at-home post-operative monitoring and automated Clinical care escalation and coordination processes.
58-
59-
This architecture pattern demonstrates three strengths:
60-
61-
* Enabling healthcare at the edge
62-
** Taking healthcare past the edge of the cloud to support care processes in Low Bandwidth environments.
63-
* AI integrated into healthcare team workflows
64-
** BPM+ Health workflows support plug & play AI modules embedded into clinical workflows as Clinical Decision Support.
65-
* Event driven, Intelligent automation
66-
** Clinical best practices & processes automated using BPM+ Health authored workflows using FHIR API endpoints.
67-
68-
For a thorough explanation of this solution in the context of Sepsis detection please consider reviewing the following 25 minute video.
69-
70-
// video link to a presentation on the use case
71-
.Overview of the solution in Sepsis Detection
72-
video::VHjpKIeviFE[youtube]
73-
74-
== Pattern Architecture Overview
75-
76-
As data arrives from Alani's various monitoring devices her latest metrics are collected in the FHIR database. Debezium is an open source distributed platform for change data capture. It will create an observation bundle for streaming to the AI model. This, in turn, will create a risk assessment and provide that to the process automation for review with Alani's doctor or the on-call doctor that is available. Their assessment may trigger further process workflows.
77-
78-
79-
80-
//figure 1 originally
81-
.Overview of the solution reference architecture
82-
image::emerging-disease-detection/edd-reference-architecture.png[link="/images/emerging-disease-detection/edd-reference-architecture.png"]
83-
84-
In the following figure, logically, this solution can be viewed as being composed of an automation component, unified management including secrets management, and the clusters under management, all running on top of a user-chosen mixture of on-premise data centers and public clouds.
85-
86-
//figure 2 originally
87-
.Sepsis Data Architecture
88-
image::emerging-disease-detection/edd-data-architecture.png[link="/images/emerging-disease-detection/edd-data-architecture.png", width=940]
89-
90-
//figure 3 logical
91-
.Logical Architecture
92-
image::emerging-disease-detection/edd-logical-architecture-legend.png[link="/images/emerging-disease-detection/edd-logical-architecture-legend.png", width=940]
93-
94-
//figure 4 Schema
95-
.Data Flow Architecture
96-
image::emerging-disease-detection/edd-schema-dataflow.png[link="/images/emerging-disease-detection/edd-schema-dataflow.png", width=940]
97-
98-
[id="about-technology"]
99-
== About the technology
100-
101-
The following technologies are used in this solution:
102-
103-
https://www.redhat.com/en/technologies/cloud-computing/openshift/try-it[Red Hat OpenShift Platform]::
104-
An enterprise-ready Kubernetes container platform built for an open hybrid cloud strategy. It provides a consistent application platform to manage hybrid cloud, public cloud, and edge deployments. It delivers a complete application platform for both traditional and cloud-native applications, allowing them to run anywhere. OpenShift has a pre-configured, pre-installed, and self-updating monitoring stack that provides monitoring for core platform components. It also enables the use of external secret management systems, for example, HashiCorp Vault in this case, to securely add secrets into the OpenShift platform.
105-
106-
https://www.redhat.com/en/technologies/cloud-computing/openshift/try-it[Red Hat OpenShift GitOps]::
107-
A declarative application continuous delivery tool for Kubernetes based on the ArgoCD project. Application definitions, configurations, and environments are declarative and version controlled in Git. It can automatically push the desired application state into a cluster, quickly find out if the application state is in sync with the desired state, and manage applications in multi-cluster environments.
108-
109-
https://www.redhat.com/en/technologies/management/ansible[Red Hat Ansible Automation Platform]::
110-
Provides an enterprise framework for building and operating IT automation at scale across hybrid clouds including edge deployments. It enables users across an organization to create, share, and manage automation, from development and operations to security and network teams.
11129

112-
https://www.redhat.com/en/technologies/jboss-middleware/amq[Red Hat AMQ Streams]::
113-
Red Hat AMQ streams is a massively scalable, distributed, and high-performance data streaming platform based on the Apache Kafka project. It offers a distributed backbone that allows microservices and other applications to share data with high throughput and low latency. Red Hat AMQ Streams is available in the Red Hat AMQ product.
30+
include::modules/edd-about-emerging-disease-detection.adoc[leveloffset=+1]
11431

115-
https://marketplace.redhat.com/en-us/products/red-hat-single-sign-on[Red Hat Single Sign-On]::
116-
Based on the Keycloak project, Red Hat Single Sign-On enhances security by enabling you to secure your web applications with Web single sign-on (SSO) capabilities based on popular standards such as SAML 2.0, OpenID Connect and OAuth 2.0.
32+
include::modules/edd-architecture.adoc[leveloffset=+1]
11733

118-
Hashicorp Vault::
119-
Provides a secure centralized store for dynamic infrastructure and applications across clusters, including over low-trust networks between clouds and data centers.
34+
[id="next-steps_edd-index"]
35+
== Next steps
12036

121-
This solution also uses a variety of _observability tools_ including the Prometheus monitoring and Grafana dashboard that are integrated with OpenShift as well as components of the Observatorium meta-project which includes Thanos and the Loki API.
37+
* link:edd-getting-started[Deploy the management hub] using Helm.
Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,17 @@
1+
---
2+
title: Getting started
3+
weight: 10
4+
aliases: /emerging-disease-detection/getting-started/
5+
---
6+
:toc:
7+
:imagesdir: /images
8+
:_content-type: ASSEMBLY
9+
10+
include::modules/edd-deploying-edd-pattern.adoc[leveloffset=1]
11+
12+
include::modules/edd-using-edd-pattern.adoc[leveloffset=1]
13+
14+
= Next Steps
15+
16+
link:https://groups.google.com/g/hybrid-cloud-patterns[Help & Feedback]
17+
link:https://github.com/validatedpatterns/emerging-disease-detection/issues[Report Bugs]
Lines changed: 47 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,47 @@
1+
:_content-type: CONCEPT
2+
:imagesdir: ../../images
3+
4+
[id="about-emerging-disease-detaction-pattern"]
5+
= About the Emerging Disease Detection pattern
6+
7+
Use case::
8+
9+
* Use a GitOps approach to manage a hybrid cloud deployment for an AI emerging disease detection system.
10+
* Use a AI automation at the edge to detect emerging diseases.
11+
* Use an event driven architecture
12+
* Enable application lifecycle management.
13+
* Securely manage secrets across the deployment.
14+
+
15+
Background::
16+
No technology is better poised to transform Healthcare as AI and Business Process Automation. Coupled with an Edge Architecture, these continuous monitoring and detection systems can scale to provide early warning intervention and measurable process improvements, anywhere.
17+
18+
Detection of disease states like sepsis, stroke, pulmonary embolism, and heart attack requires low-latency, broadband, asynchronous streaming capabilities. We have prototyped an early warning platform built with a distributed edge architecture, fed by at-home post-operative monitoring (fitbit, smart phone, wifi devices) and automated Clinical care escalation and coordination processes. This platform has the potential to significantly lower network traffic and cost while providing early warning interventions for our nation's Veterans.
19+
20+
[id="about-solution"]
21+
== About the solution
22+
23+
To demonstrate the effectiveness of the solution this pattern focuses on the specific problem of Sepsis. Sepsis is the body's extreme response to an infection. It is a life-threatening medical emergency. Sepsis is a costly and life threatening condition that can result in multi-organ failure. Beating conditions like sepsis requires rapid detection and mitigation of risks. With the immune system compromised, recovery at home is often preferred to minimize the risk for cross-infections, yet medical teams often lack the capability to perform constant surveillance for emerging risks across their patient cohorts, especially in rural settings. In this session, we will demonstrate an early warning system driven by Clinical AI at the Edge, fed by at-home post-operative monitoring and automated Clinical care escalation and coordination processes.
24+
25+
== Technology Highlights:
26+
* Event-Driven Architecture
27+
* Data Science on OpenShift
28+
* Process Automation
29+
30+
== Solution Discussion and Demonstration
31+
In this demonstration, we will follow a vulnerable, post-operative patient, Alani, as she recovers from surgery in her home setting. The pattern demonstrates an early warning system driven by Clinical AI at the Edge, fed by at-home post-operative monitoring and automated Clinical care escalation and coordination processes.
32+
33+
This architecture pattern demonstrates three strengths:
34+
35+
* Enabling healthcare at the edge
36+
** Taking healthcare past the edge of the cloud to support care processes in Low Bandwidth environments.
37+
* AI integrated into healthcare team workflows
38+
** BPM+ Health workflows support plug & play AI modules embedded into clinical workflows as Clinical Decision Support.
39+
* Event driven, Intelligent automation
40+
** Clinical best practices & processes automated using BPM+ Health authored workflows using FHIR API endpoints.
41+
42+
For a thorough explanation of this solution in the context of Sepsis detection please consider reviewing the following 25 minute video.
43+
44+
// video link to a presentation on the use case
45+
.Overview of the solution in Sepsis Detection
46+
video::VHjpKIeviFE[youtube]
47+

modules/edd-architecture.adoc

Lines changed: 50 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,50 @@
1+
:_content-type: CONCEPT
2+
:imagesdir: ../../images
3+
4+
[id="overview-architecture"]
5+
== Overview of the Architecture
6+
7+
As data arrives from Alani's various monitoring devices her latest metrics are collected in the FHIR database. Debezium is an open source distributed platform for change data capture. It will create an observation bundle for streaming to the AI model. This, in turn, will create a risk assessment and provide that to the process automation for review with Alani's doctor or the on-call doctor that is available. Their assessment may trigger further process workflows.
8+
9+
//figure 1 originally
10+
.Overview of the solution reference architecture
11+
image::emerging-disease-detection/edd-reference-architecture.png[link="/images/emerging-disease-detection/edd-reference-architecture.png"]
12+
13+
In the following figure, logically, this solution can be viewed as being composed of an automation component, unified management including secrets management, and the clusters under management, all running on top of a user-chosen mixture of on-premise data centers and public clouds.
14+
15+
//figure 2 originally
16+
.Sepsis Data Architecture
17+
image::emerging-disease-detection/edd-data-architecture.png[link="/images/emerging-disease-detection/edd-data-architecture.png", width=940]
18+
19+
//figure 3 logical
20+
.Logical Architecture
21+
image::emerging-disease-detection/edd-logical-architecture-legend.png[link="/images/emerging-disease-detection/edd-logical-architecture-legend.png", width=940]
22+
23+
//figure 4 Schema
24+
.Data Flow Architecture
25+
image::emerging-disease-detection/edd-schema-dataflow.png[link="/images/emerging-disease-detection/edd-schema-dataflow.png", width=940]
26+
27+
[id="about-technology"]
28+
== About the technology
29+
30+
The following technologies are used in this solution:
31+
32+
https://www.redhat.com/en/technologies/cloud-computing/openshift/try-it[Red Hat OpenShift Platform]::
33+
An enterprise-ready Kubernetes container platform built for an open hybrid cloud strategy. It provides a consistent application platform to manage hybrid cloud, public cloud, and edge deployments. It delivers a complete application platform for both traditional and cloud-native applications, allowing them to run anywhere. OpenShift has a pre-configured, pre-installed, and self-updating monitoring stack that provides monitoring for core platform components. It also enables the use of external secret management systems, for example, HashiCorp Vault in this case, to securely add secrets into the OpenShift platform.
34+
35+
https://www.redhat.com/en/technologies/cloud-computing/openshift/try-it[Red Hat OpenShift GitOps]::
36+
A declarative application continuous delivery tool for Kubernetes based on the ArgoCD project. Application definitions, configurations, and environments are declarative and version controlled in Git. It can automatically push the desired application state into a cluster, quickly find out if the application state is in sync with the desired state, and manage applications in multi-cluster environments.
37+
38+
https://www.redhat.com/en/technologies/management/ansible[Red Hat Ansible Automation Platform]::
39+
Provides an enterprise framework for building and operating IT automation at scale across hybrid clouds including edge deployments. It enables users across an organization to create, share, and manage automation, from development and operations to security and network teams.
40+
41+
https://www.redhat.com/en/technologies/jboss-middleware/amq[Red Hat AMQ Streams]::
42+
Red Hat AMQ streams is a massively scalable, distributed, and high-performance data streaming platform based on the Apache Kafka project. It offers a distributed backbone that allows microservices and other applications to share data with high throughput and low latency. Red Hat AMQ Streams is available in the Red Hat AMQ product.
43+
44+
https://marketplace.redhat.com/en-us/products/red-hat-single-sign-on[Red Hat Single Sign-On]::
45+
Based on the Keycloak project, Red Hat Single Sign-On enhances security by enabling you to secure your web applications with Web single sign-on (SSO) capabilities based on popular standards such as SAML 2.0, OpenID Connect and OAuth 2.0.
46+
47+
Hashicorp Vault::
48+
Provides a secure centralized store for dynamic infrastructure and applications across clusters, including over low-trust networks between clouds and data centers.
49+
50+
This solution also uses a variety of _observability tools_ including the Prometheus monitoring and Grafana dashboard that are integrated with OpenShift as well as components of the Observatorium meta-project which includes Thanos and the Loki API.

content/patterns/emerging-disease-detection/getting-started.adoc renamed to modules/edd-deploying-edd-pattern.adoc

Lines changed: 4 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,8 @@
1-
---
2-
title: Getting Started
3-
weight: 10
4-
aliases: /emerging-disease-detection/getting-started/
5-
---
1+
:_content-type: PROCEDURE
2+
:imagesdir: ../../../images
63

7-
:toc:
8-
:imagesdir: /images
9-
:_content-type: ASSEMBLY
4+
[id="deploying-edd-pattern"]
5+
= Deploying the Emerging Disease Detection pattern
106

117
== Prerequisites
128

@@ -219,11 +215,3 @@ The most important ArgoCD instance to examine at this point is `emerging-disease
219215

220216
. Check all applications are synchronised. There are thirteen different ArgoCD "applications" deployed as part of this pattern.
221217

222-
[id="viewing-the-sepsis-application-dashboard-getting-started"]
223-
== Viewing the Sepsis Detection dashboard
224-
TO-DO: Describe how to examine the various parts of the Sepsis application
225-
226-
= Next Steps
227-
228-
link:https://groups.google.com/g/validatedpatterns[Help & Feedback]
229-
link:https://github.com/validatedpatterns/emerging-disease-detection/issues[Report Bugs]

modules/edd-using-edd-pattern.adoc

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
:_content-type: PROCEDURE
2+
:imagesdir: ../../../images
3+
4+
[id="deploying-edd-pattern"]
5+
= Using the Emerging Disease Detection pattern
6+
7+
The following steps describes how you can use this pattern in a demo.
8+
9+
== Viewing the Sepsis Detection dashboard
10+
TO-DO: Describe how to examine the various parts of the Sepsis application
212 KB
Loading

0 commit comments

Comments
 (0)