Biomedical Informatics and Data Science, BS program guide

Current program identity

Are you interested in bridging your interests in technology and health care? Gain expertise in translating biomedical data into knowledge that improves individual and population health outcomes.

ASU Degree Search is the public identity source for this BS path and plan code ESBMIBS. Undergraduate curriculum groups come from the current 2026 checksheet; graduate class codes come from the active Degree requirements area. The Fall 2026 course catalog supplies class titles and descriptions. These layers describe public structure, not a personal enrollment contract.

Before scheduling support, reconcile this map with the current degree audit or iPOS. Confirm catalog year, campus or online modality, admission status, prerequisites, transfer work, concurrent or accelerated arrangements, electives, substitutions, clinical placement, and advisor approval. Preserve alternatives as alternatives. A course listed inside an elective group is not automatically required for every student.

The classes, one by one

Open a code for its full class guide, current catalog focus, every mapped program context, session boundary, rubric workflow, grade controls, and right-side navigation. Shared classes own one canonical page so their guidance cannot drift between degrees.

Biomedical Informatics and Data Science, BS · Major Core Courses

Biomedical Informatics and Data Science, BS · Computer Science Courses

Biomedical Informatics and Data Science, BS · College of Health Solutions Requirements

Biomedical Informatics and Data Science, BS · Foundational Courses

Biomedical Informatics and Data Science, BS · ASU 101 or college-specific equivalent First-Year Seminar required of all first-year students.

Biomedical Informatics and Data Science, BS · First-Year Composition

Program → class → Week or live Canvas syllabus

ASU uses Session A, Session B, and Session C at registration level, but a program page does not establish one universal class length. No generic Week layer is generated here. The registered schedule and Canvas syllabus control the actual cadence.

For each registered class, copy section, instructor, start and end dates, Session A, B, or C designation, due-day pattern, time zone, grading model, late policy, required technology, and final-submission window from My ASU and Canvas. Then inventory the real work: discussions, replies, quizzes, papers, cases, presentations, projects, labs, simulations, clinical or practicum records, and exam-preparation blocks.

A Week number is a position, not an assessment identity. Preserve the exact live title, directions, rubric version, template, permitted sources and tools, point value or weight, file type, deadline, and submission location before production. Announcements that amend a requirement belong in the same control packet.

Build the session board

Give every obligation one row with class code, exact Canvas label, session and Week or date, due time and time zone, points or category weight, dependency, evidence need, permitted tools, current status, feedback status, and next action. Keep different work types separate because a discussion, quantitative problem, presentation, clinical record, and proctored-exam preparation block do not share one completion test.

Work backward from the deadline. Reserve intake time for directions and rubric, evidence time for research or data, production time for the actual deliverable, and a delivery pass for citations, accessibility, filename, file type, export, and upload rendering. A 7.5-week class compresses these blocks; it does not remove them.

Reconcile after every posted result. Use raw points only when the syllabus is points-based; calculate weighted categories independently when weights control. Keep full precision until display and track any separate exam-average, clinical, competency, attendance, or progression floor as its own gate.

Turn the live rubric into acceptance tests

Directions and rubric are separate contracts. Directions control scenario, audience, length, format, source limits, tools, and submission rules. Rubric rows control scoring evidence. Translate each requirement into a yes-or-no test and assign it a visible destination in the paper, calculation, presentation, care document, project file, or discussion.

Read verbs literally. Describe requires accurate coverage; compare requires a visible basis; analyze requires relationships and implications; evaluate requires criteria and judgment; recommend requires a defensible choice tied to evidence. Universal words such as all, each, and every change the minimum complete response.

Run content quality before delivery quality. Check coverage, logic, evidence quality, calculations, and consistency across prose, tables, figures, slides, and appendices. Then check citation matching, template fields, accessibility, filename, file type, and rendered export. A polished file cannot compensate for a missing decision, and good analysis can still fail when the wrong file is uploaded.

Clinical, professional, and exam boundaries

Students perform patient care, clinical decisions, skills, simulations, laboratory activity, practicum or rotation hours, preceptor communication, signatures, experience logs, group participation, identity-verified activity, and final submission. Remove protected health, client, employee, and proprietary information before any tutoring review.

Proctored, standardized, competency, dosage-calculation, readiness, and licensure-related assessments are preparation-only. Legitimate support includes a study blueprint, practice questions, rationale review, calculation practice, concept explanation, rehearsal, and readiness decisions. It does not include entering an authenticated environment or completing the real assessment.

Questions about this ASU program