Loading...
Users can record and transcribe audio for a patient session
Users can get gen AI summaries of their notes
Users can load their notes
Audio is transcribed near real time
AI summaries are available within 30s of ending session
Audio is not retained
Support 500 daily users (4 sessions per day, 60 minutes session average)
audio recording/transcribing
generate note summary
retrieve note summary
assuming sql
user
id: primary key, uuid
created_at: datetime
notes
id: pk, uuid
session_id: fk session.id
text: string
created_at: datetime
session
id: pk, uuid
user_id: fk user.id
patient_id: fk patient.id
created_at: datetime
transcription
id: pk, uuid
session_id: fk session.id
contents: string
patient
id: pk, uuid
user_id: fk user.id
created_at: datetime
You should identify enough components that are needed to solve the actual problem from end to end. Also remember to draw a block diagram using the diagramming tool to augment your design. If you are unfamiliar with the tool, you can simply describe your design to the chat bot and ask it to generate a starter diagram for you to modify...
Explain how the request flows from end to end in your high level design. Also you could draw a sequence diagram using the diagramming tool to enhance your explanation...
Dig deeper into 2-3 components and explain in detail how they work. For example, how well does each component scale? Any relevant algorithm or data structure you like to use for a component? Also you could draw a diagram using the diagramming tool to enhance your design...
Explain any trade offs you have made and why you made certain tech choices...
Try to discuss as many failure scenarios/bottlenecks as possible.
What are some future improvements you would make? How would you mitigate the failure scenario(s) you described above?