Architecture Diagram of Complete MVP

[wiredsister]

Components

• OCaml Rules Engine (Matching - Policy)
• Phoenix WebAPI (Integrations & API Layer)
• Web GUIs (Patient, OPO, Surgeon)
• Data Warehouse Solution (Data Scientists & Researchers)
• Kafka (Triggers & Event Driven System Behavior)

[wiredsister]

[yanlow]

@wiredsister lmk when you want to review this, let's give it an hour or two. We should be able to determine the following:

• external/internal service names
• expected traffic
• topic identifiers
• suitability of Kubernetes/Terraform config Terraform scripts #8
• outbound request caching How to be a considerate API user? How to scale integrations? #12

[wiredsister]

What types of features from Kubernetes do you see our project specifically benefitting from? Love the idea of Terraform wrapping Kub8s...

[MeredithStewart]

@wiredsister - note that for the GUIs, we probably don't have a patient interface.

[wiredsister]

Right, I do think we should have clinicians onboard patients though and have a "patient profile" ish. That way we have a way to communicate with patients about contacting them for approval (think in the circumstance of someone who needs a 3rd party for medical needs), have them update their location information (maybe they are willing to travel for surgery?), post-op outcomes and self-reported medical device telemetry, etc.

organ_lifecycle.pdf

[MeredithStewart]

It might be empowering for those individuals on the waitlist to have any information or tooling for themselves. Hypothetically could engage more in their own care and decision making.

[wiredsister]

Yeah, I think so, right? They could do approvals (for 3rd party authorization or someone making medical decisions on behalf) or just the patient who wants to make sure their latest results are accurate and their contact information is up to date. I think there is really high value in having a Patient as a user in the system. And what's great is they wouldn't have to share their data with anyone except the matching algorithms' systems and our database. No leaking data to providers and labs at every step. We present it to those teams when they need it in select ways and then archive it.

[MeredithStewart]

We should try to get some validation of the patient as a user. I'm thinking actually interviewing some patients and surgeons. We can ask OPOs, but I'm not sure if they've got that perspective really of the patient waiting for the transplant.