Breya Academy

Breya Medical Career Explorer

The medical–technology intersection

A technical career exploration hub for high school students building professional agency and technical domain expertise, through inquiry, analysis, and respect for clinical practice.

Four domains

Where technical depth meets patient outcomes

Select a quadrant to emphasize it. Each pairs a core skill with a real-world impact practitioners defend every day.

Career blueprint library

Technical blueprints, not business plans

Each card is a technical shadow roadmap: what practitioners set up, what problems they interrogate, and what an entry-level contributor might ship. Use search to narrow roles by keyword (e.g., “FHIR”, “DICOM”, “QC”).

Students working with microscope and lab notes in a science classroom

Real lab benches where technical blueprints meet hands-on inquiry

8 roles match

Bio-Informatics Scientist
Builds reproducible pipelines from sequence to insight: reference genomes, QC, and reviewer-ready provenance.

Technical shadow roadmap

1

Phase 1 · Tooling & environment

Linux shell, workflow managers (e.g., Nextflow concepts), Python/R notebooks, version control, container basics.

2

Phase 2 · Problem identification

Variant calling confidence, batch effects, cohort inclusion rules: what in the data could mislead a clinician?

3

Phase 3 · Technical contribution

Re-run a QC report on a mock batch, document one parameter change, and explain patient-risk if it were wrong.

Clinical Informatics Analyst
Maps workflows to systems: orders, results, alerts, and proves information is complete for the chart.

Technical shadow roadmap

1

Phase 1 · Tooling & environment

EHR sandboxes or read-only demos, interface engines, spreadsheet + diagram tools, basic SQL.

2

Phase 2 · Problem identification

Duplicate alerts, broken result routing, missing discrete data: where does the chart diverge from bedside truth?

3

Phase 3 · Technical contribution

Draft a swimlane for one order type and list three data elements that must be discrete for reporting.

Health Data Engineer
Moves PHI safely between systems with lineage: pipelines analysts and practitioners can audit.

Technical shadow roadmap

1

Phase 1 · Tooling & environment

ELT patterns, IAM-style access models, orchestration, observability dashboards for pipeline health.

2

Phase 2 · Problem identification

Late files, schema drift, re-identification risk: what breaks trust in a Monday-morning metrics meeting?

3

Phase 3 · Technical contribution

Sketch a one-table lineage diagram (source → transform → dashboard) with one privacy checkpoint labelled.

Medical Mechatronics Technologist
Bridges firmware, mechanics, and clinical use; devices must behave under stress and be serviceable.

Technical shadow roadmap

1

Phase 1 · Tooling & environment

Oscilloscope mindset (even in simulation), CAD awareness, embedded C/Python, bench test scripts.

2

Phase 2 · Problem identification

Sampling jitter, alarm latency, power loss behaviour: when does the device become a patient-risk surface?

3

Phase 3 · Technical contribution

Write a three-step bench test plan after a hypothetical sensor firmware bump: expected vs. failure signal.

Digital Therapeutics Designer
Designs measured interventions: flows, copy, and telemetry aligned to clinical endpoints.

Technical shadow roadmap

1

Phase 1 · Tooling & environment

Figma or equivalent, content design systems, analytics event schemas, accessibility checklists.

2

Phase 2 · Problem identification

Drop-off, misunderstood dosing instructions, missing escalation paths: where does efficacy leak?

3

Phase 3 · Technical contribution

Prototype one screen revision and define two analytics events that prove adherence, not vanity clicks.

Regulatory Technology Specialist
Turns standards into systems: trace matrices, e-signatures, and evidence packages reviewers can navigate.

Technical shadow roadmap

1

Phase 1 · Tooling & environment

QMS portals, requirements tools, automated test evidence capture, controlled document workflows.

2

Phase 2 · Problem identification

Ambiguous intended use, untraceable changes, incomplete risk files: what would stall an inquiry?

3

Phase 3 · Technical contribution

Create a mini trace row: one requirement → one test → one release note line (mock content).

Clinical Decision Support Analyst
Tunes rules and models so prompts help without hijacking clinician judgment.

Technical shadow roadmap

1

Phase 1 · Tooling & environment

Rules engines, BI for alert metrics, cohort builders, versioned artifact repositories.

2

Phase 2 · Problem identification

Alert fatigue, overridden critical warnings, demographic bias: what would an inquiry ask first?

3

Phase 3 · Technical contribution

Propose one guardrail (e.g., suppressions with audit) and define the metric to prove it helped.

Imaging Informatics Specialist
Keeps imaging available, comparable, and secure, from modality to PACS/VNA to AI overlays.

Technical shadow roadmap

1

Phase 1 · Tooling & environment

DICOM browsers, routing logs, viewer integrations, storage tiering concepts.

2

Phase 2 · Problem identification

Lossy transforms, wrong laterality, priors mismatch: where does diagnosis silently degrade?

3

Phase 3 · Technical contribution

Document one realistic failure mode and the log line or tag that would expose it in practice.

Deep work · skill lab

Projects that stress-test these careers

Short, serious builds you can run in a studio block. Each project foregrounds analysis and inquiry, the same habits technical domains reward in clinical practice.

Students in a health sciences learning environment with instructors
Peer pair at a microscope documenting observations
Focused student work at a lab bench with protective equipment
A

Project A

Build a HIPAA-compliant patient intake form

Design fields, consent copy, and a data-minimization map: what is collected, why, and where it may flow. Add a short analysis of common misconfigurations (e.g., insecure transmission) and how you would prevent them.

Privacy engineering · form design · policy literacy

B

Project B

Design a telehealth interface for elderly users

Large-target layouts, hearing and vision affordances, and a clear escalation path to a human clinician. Validate with a scripted usability walkthrough and document findings as an inquiry log, not a slide deck.

Inclusive UX · clinical communication · safety pathways

C

Project C

Analyse a (mock) genomic dataset for anomalies

Import a small synthetic VCF or summary table, flag outliers, and write a one-page methods note: references, QC gates, and what you would not claim without wet-lab confirmation.

Bio-informatics · QC discipline · honest reporting

Mentorship connect

Connect for structured inquiry and analysis

Educators and students can request blueprint packets, guest practitioner alignment, or district-safe next steps. We route requests through our desk with the same rigor as a clinical handoff: clear role, scope, and follow-up accountability.

  • Grounded in technical domain expertise and classroom feasibility
  • Language of inquiry, analysis, and clinical practice only
  • Optional alignment to a specific blueprint card you searched above
Two healthcare professionals in scrubs collaborating at a laptop in a clinical learning setting