medic-code / embolism Goto Github PK

Using data, diagrams and tables to illustrate acute pulmonary embolism's clinical and pathophysiological aspects uniquely not captured in textbooks. The idea is to use selective previously published research data to enhance the well known knowledge that is derived from these studies in a more apparent way. This will cover various clinical aspects of the topic using data to highlight the points as well as highlighting pathophysiology in a data driven way that not only describes the pathophysiology of the topic but to quantify this using numbers where possible. Using published data and interaction combined brings content alive that engages the users rather than makes them want to shut off.

To come up with the Big idea for the scrollytelling essay

Symptoms of PE

Diagnostic Data of PE

Pathophysiology
Mechanical Occulsion
V/Q Mismatch
Chemical Mediators
Alveolar hypoxaemia

Haemodynamic consequences
	increased RV afterload
	Decreased filling of LV 

Pulmonary Infarction 

Risk stratification
Systolic below 90
RV Dysfunction

Mortality rate with severity

D-Dimer lab specs

One of the troubles with essays and retention is that you don't remember what you've read. One of the problems is that the questions you create are best coming from yourself. The barrier seems to high to allow users to create their own questions. Set questions and set answers seems like a good first step.

Technical Requirements

User perspective
React will be able to handle interactivity

1. User activated questions on scrolling
2. Question up on screen as user scrolls down the page
3. Buttons for easy, medium, hard or don't remember so to click it triggers the answer to appear on the screen.
4. Consider the algorithm used for spaced repetition to incorporate (Anki uses SM-2)
5. Somewhere on the question (top right-hand corner) to outlay how many questions in total in the deck
6. End screen when finished deck
7. Button to review again
8. At the end of the essay, be able to export questions/answers to space repetition program of choice ?
9. Be able to toggle that functionality to force reader to remember (ie after a first read ?)

Data Persistence
Will need a way to store questions and answers on the page. If it was, maybe a couple of sections could perhaps get away with hard coding answers and questions. If we get to more than 10-15 questions on a page, I think a database table of question and answer might be more appropriate.

For now, seems like hard coding may be the way forward unless we come up again pain points.