-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathindex.html
140 lines (123 loc) · 5.95 KB
/
index.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<title>US Healthcare System Map</title>
<meta name="title" property="og:title" content="US Healthcare System Map">
<meta name="description" property="og:description" content="">
<link href="https://fonts.googleapis.com/css2?family=Source+Sans+Pro:wght@400;700&display=swap" rel="stylesheet">
<link rel="stylesheet" href="./css/site.css">
</head>
<body>
<header></header>
<div class="container">
<h1>
US Healthcare System Map</h1>
<p>An opensource work in progress by
<a href="https://www.goinvo.com/" target="_blank">GoInvo</a>
<br>
<a href="https://docs.google.com/presentation/d/19u9JrRphb2qaPcgkEq9vaE9f2aCWsUfI3L75B2PT47g/edit?usp=sharing">Draft project outline</a>
<br>
Last update on 28.Nov.2022.
<br>
Send us your feedback at [email protected]
<br>
<br>
</p>
<h2>Problem</h2>
<p>There is no single diagram or map of the US healthcare system that effectively describes the main actors and relationships between actors.
<br>
<br>
Unfortunately, current healthcare system maps are too narrowly focused and/or struggle to clarify the complexity of the system (see examples below). The US healthcare system is complex, and we (healthcare policy makers, patients, medical students, etc) would benefit from a dynamic System Map.
</p>
<div>
<img src="./images/past_examples.png"/>
</div>
<h2>Our Goal</h2>
<p>Our goal at GoInvo is to create and open source map of the US healthcare system. Currently, we are in the process of outlining and designing the map. Ultimately, we hope to build an interactive, mobile-friendly map.</p>
<h2>Impact</h2>
<p>We hope to not only shine a light on the structure of the US healthcare system but to create an opensource resource for academics, healthcare analysts, health IT engineers and designers, entrepreneurs finding their place in the system, healthcare governance and policymakers, patients, and more.</p>
<h2>Initial Work</h2>
<h3>Early Concepts</h3>
<p>We began by mapping out governance bodies.</p>
<div>
<img src="./images/governance_map.png"/>
</div>
<p>This kind of hierarchical diagram became lengthy very quickly, so we started to explore a layout and map that could reflect various key roles in the Healthcare System (Research, Pharma, Care, Payment).</p>
<div>
<img src="./images/hc_sys_map_dan1.png"/>
</div>
<div>
<img src="./images/hc_sys_map_dan2.png"/>
</div>
<h3>Data Model</h3>
<p>As we dug deeper and got a feel for the actors at play, we explored data models to represent the complexity of different types of players, their organization, and the relationships between them. This allowed us to step sideways from the challenge of visualizing the system, and focus on describing or defining the system in parallel. With a robust data model and database in hand, we will construct custom views to zero in on whatever lens, and facet, or detail is of interest in the system.</p>
<a href="https://airtable.com/shrn8nBZKLQSGUDGN" target="_blank">
<br/>
<button>
View our Data Model in AirTable
</button>
<br/>
</a>
<div>
<img src="./images/data_model.png"/>
</div>
<h3>Mapping Roles VS Entities</h3>
<p>Going through this process, we realized that "Entities" (like CVS) hardly ever stick to consistent "Roles" (such as filling prescriptions). Even in that example, CVS expands their role to Pharmacy benefit
Manager and even some primary care delivery. Trying to create a map that shows how all of these Roles fit together is nearly impossible because each Entity often expands their roles in different ways. Healthcare
isn't clear cut. One way to handle this complexity is to map out general roles and then place entities on top of that map. See the examples below.
<div>
<img src="./images/hc_roles_map.png"/>
</div>
<p>In this final concept, we look at a potential way to interact with the diagram.
<br>
<br>
Mapping Entities onto the Landscape of HC Roles
<br>
(note: this diagram isn’t comprehensive. We've kept it simple for proof of concept)
<br>
1. View the whole landscape
of high level roles in healthcare.
</p>
<div>
<img src="./images/patient_centered_map_1.png"/>
</div>
<p>2. Click on one of the Roles/Categories to learn more about it and how it connects to other roles.</p>
<div>
<img src="./images/patient_centered_map_2.png"/>
</div>
<p>3. Explore specific entities (such as CVS in this case) which may perform more than one role.</p>
<div>
<img src="./images/patient_centered_map_3.png"/>
</div>
<p>General layout/organization of information focused on role based categories.</p>
<div>
<img src="./images/patient_centered_map_4.png"/>
</div>
<p>Still working on what are the Roles/Categories and which ones are CONNECTED.
<br> Note that any specific entity such as FDA would show up in the same kind of way that CVS did,
highlighting any role it plays. Ideally, the sizes and shapes would be meaningful (right now they
are just about defining connection to other roles). I’ve clarified and determined more of an
organizational layout (above). We should update this based on that thinking. </p>
<div>
<img src="./images/patient_centered_map_5.png"/>
</div>
<h3>
<br>
<br>
Have feedback?
<br>
Share it with us at [email protected]
<br>
<br>
<br>
<br>
<br>
</h3>
</div>
<footer>
<div class="container">
<div>Licensed by <a href="https://www.goinvo.com/" target="_blank">GoInvo</a> under the <a href="https://www.apache.org/licenses/LICENSE-2.0" target="_blank">Apache</a> open source license in 2022</span>
</div>
</footer>
</body>
</html>