For clinicians who buildMD-dev

what changed for clinicians of any background building their own software with ai — coding agents, models, health data access, privacy & the rules — checked daily, each note against at least two sources


Rules & guidance · 3 notes · newest first

HHS finalizes HIPAA Privacy Rule update: 15-day access deadline, health app copies

The HHS Office for Civil Rights (OCR) issued a final rule amending the HIPAA Privacy Rule on November 16, 2026, with Federal Register publication on November 19. It cuts the standard deadline for answering a patient's records request from 30 to 15 calendar days (a one-time extension is still allowed), and it bars unreasonable identity-verification steps. It also says patients can have their electronic records sent to a personal health application they control when the covered entity is able to provide them in that form, and it revises the permitted fees for access requests. The rule takes effect January 18, 2027, and covered entities and business associates must comply by July 17, 2027. A separate overhaul of the HIPAA Security Rule was not finalized, and reporting says it is on hold until at least mid-2027.

Why it's notable: Clinicians at covered practices who build record-request workflows or patient-facing apps will be working against a 15-day standard deadline and an explicit provision for delivering records to a patient's chosen app. Check the final text for exactly when the app requirement applies to your organization.

#HIPAA#HHS OCR#right of access#personal health apps

ONC finalizes HTI-5, dropping 14 certification criteria and AI transparency rules

On October 26, 2026, HHS's Office of the National Coordinator for Health IT (ONC/ASTP) released the HTI-5 final rule. It removes 14 of the 60 criteria in the Health IT Certification Program (the federal checklist EHR software must meet to be 'certified') and revises seven, far fewer than the 34 removals proposed in December 2025. The decision support interventions criterion no longer requires certified EHRs to show 'source attributes' (model-card style information) or apply risk management to predictive AI tools, and ONC finalized none of its proposed changes to the information blocking rules, which stay in force. According to the AHA and McGuireWoods, 13 changes take effect December 28, 2026, seven on January 1, 2027, and one on January 1, 2030. HHS estimates more than $1.55 billion in present-value savings.

Why it's notable: If you rely on your EHR's built-in AI or decision support, certified systems no longer have to tell you where a predictive model came from or how it was tested, so ask your vendor directly. Patient and clinician data access rights under the information blocking rules are unchanged, and ONC says it is resetting the program to build future FHIR-based API requirements, which McGuireWoods says include APIs that move beyond read-only access.

#ONC#ASTP#HTI-5#certification
Sources: ONC / HealthIT.gov, American Hospital Association, McGuireWoods · last verified 2026-11-22

California enacts AB 1979 and SB 503 setting rules for clinical AI tools

On September 30, 2026, Governor Gavin Newsom signed AB 1979 and SB 503, both effective January 1, 2027. AB 1979 requires California health facilities, clinics and physician offices to take reasonable steps to ensure that a licensed provider exercises independent judgment whenever AI output informs patient care, and it bars AI from independently performing functions reserved for licensed professionals. Licensing boards enforce those provisions; scheduling and routine reminders are exempt. AB 1979 also treats businesses offering health care chatbots to consumers as providers under the state's Confidentiality of Medical Information Act (CMIA). SB 503 applies to clinical decision support systems, defined as AI that produces a prediction, classification, recommendation or analysis aiding decisions on timing of care, diagnosis or treatment. It requires their developers and deployers to make reasonable efforts to identify and reduce biased results, and requires developers to give deployers documentation on training data, testing, intended use, risks and monitoring.

Why it's notable: SB 503 places duties on both 'developers' and 'deployers' of decision-support AI, and law-firm analyses say deployers include healthcare providers such as facilities, clinics and group practices. Whether a clinician who builds a tool falls under either term depends on the law's definitions. AB 1979 brings consumer-facing health chatbots under CMIA confidentiality duties and penalties.

#California#state law#CMIA#clinical decision support
← All topics