Medical Records Specialists
Scrub through 129years of this role's history, from when it first emerged, through every wave of technology that reshaped it, to the cited projections for where it's heading next.
The tools that defined the work
Select an era to see how it reshaped the work.
Paper dossier + pneumatic tube (Plummer unit record system, Mayo Clinic)
Henry Plummer's 1907 innovation at Mayo Clinic replaced the fragmented physician-owned ledger with a single patient dossier filed by a unique registration number. The physical record traveled through the clinic via pneumatic tube, a system the clinic maintained for decades. The record clerk's job in this era was entirely manual: writing intake information onto loose paper forms, filing numbered folders, retrieving them on request, and ensuring that every physician who saw a patient was looking at the same consolidated document. No machine assisted beyond the pneumatic tube network. The value was organizational, not mechanical: the dossier model proved that a dedicated non-clinical worker could add clinical value by managing information.
Effect on the workThe Plummer system created the template for hospital record departments nationwide, but adoption was slow. By 1919 the American College of Surgeons found that fewer than 89 of 692 US hospitals met even minimal standardization requirements. The role was created by the idea but staffed only as hospital systems were rebuilt to meet the ACS standard.
Work toolChanging equipment Standardized paper forms + the ICD (first US adoption: Statistical Manual for the Use of Institutions for the Insane, 1917; International List of Causes of Death 1920s)
The founding of the Association of Record Librarians of North America in 1928 was itself a tool-era event: it created professional standards for how paper records should be organized, what fields should be captured, and how diagnoses should be classified. The International List of Causes of Death (a forerunner of ICD) had been in use for vital statistics since the 1900s; hospitals increasingly applied disease classification systems to their records to enable epidemiological analysis and insurance billing. The record librarian's job in this era required familiarity with both filing systems and disease nomenclature, a combination of archival and quasi-clinical knowledge that set the occupation apart from general clerical work.
Effect on the workAHIMA membership grew from 35 in 1928 to nearly 4,500 by 1960, tracking the professionalization of hospital record-keeping. The ACS credentialing program (Registered Record Librarian, established 1933) raised the bar for who could manage a hospital records department, slowing informal entry but increasing the occupation's professional standing and wages.
Work toolChanging equipment Medicare, Medicaid, and ICD-8 coding (Social Security Amendments 1965)
The creation of Medicare and Medicaid in 1965 transformed medical records from an internal clinical tool into the evidentiary basis for government reimbursement. Hospitals now needed documentation not just for continuity of care but to justify every billable service to federal payers. The volume and complexity of records work expanded sharply: coding had to be accurate, diagnoses had to be supported by clinical documentation, and record-keeping staff became a financial necessity rather than a clinical convenience. When the United States began coding diagnostic information using ICD-8 (International Classification of Diseases, 8th revision) in 1968, and later ICD-9-CM in 1979, coding became a distinct technical skill requiring study and credentialing. The "accredited record technician" credential AHIMA created in 1953 took on new importance as a gateway to coding roles.
Effect on the workMedicare and Medicaid created sustained demand for records and coding staff. AHIMA membership tripled from the 1960s to 1978 (reaching 23,000), tracking the expansion of coding and compliance roles within hospital records departments.
Work toolChanging equipment DRG-based prospective payment + ICD-9-CM coding (Medicare PPS, October 1, 1983)
On October 1, 1983, Congress amended the Social Security Act to implement a nationwide Diagnosis-Related Group prospective payment system for all Medicare inpatients. Under DRG pricing, the hospital's reimbursement for an admission was determined not by the actual costs incurred but by the ICD-9-CM codes assigned to the principal diagnosis, procedures performed, and comorbidities present. Accurate coding became worth money: undercoding lost revenue, overcoding risked fraud prosecution, and the only way to get it right was to have a trained coder thoroughly review the entire medical record after every discharge. This was the moment the medical records specialist became a revenue cycle asset rather than an administrative necessity. Hospitals invested heavily in coding staff and in the emerging software systems that supported DRG assignment.
Effect on the workThe DRG system is generally credited with the professionalization and expansion of the coding workforce from the mid-1980s onward. The demand for RHIA (Registered Health Information Administrator) and RHIT (Registered Health Information Technician) credentialed coders grew substantially through the late 1980s and 1990s.
Work toolChanging equipment HIPAA Privacy and Security Rules (enacted August 21, 1996; Privacy Rule effective April 14, 2003)
The Health Insurance Portability and Accountability Act of 1996 added a new dimension to the medical records role: legal and regulatory compliance. Before HIPAA, records management was primarily about completeness and accuracy for clinical and billing purposes. After HIPAA's Privacy Rule took effect in 2003 (and its Security Rule in 2005), every person handling protected health information (PHI) became responsible for ensuring that access was authorized, disclosures were documented, and patient rights were respected. The medical records specialist became a frontline compliance worker, managing record release, maintaining access logs, and training colleagues on permissible disclosures. HIPAA compliance violations carried substantial fines, giving this administrative role a legal exposure that further elevated its standing within healthcare organizations.
Effect on the workHIPAA added compliance and legal-review tasks to a role that had previously been primarily technical and administrative. The privacy officer function, while typically held by a manager, drew heavily from the medical records professional pipeline. AHIMA membership continued growing through the HIPAA era, reaching 65,097 by 2012.
Work toolChanging equipment HITECH Act and meaningful-use EHR mandate (ARRA signed February 17, 2009)
The American Recovery and Reinvestment Act of 2009 included the HITECH (Health Information Technology for Economic and Clinical Health) Act, which committed $25.9 billion to incentivize EHR adoption, set "meaningful use" standards that hospitals had to meet to receive Medicare payments, and imposed financial penalties on providers who failed to demonstrate meaningful use by 2015. The hospital EHR adoption rate rose from roughly 9% in 2008 to 84% by 2015. For medical records specialists, the EHR transition was the single largest transformation of their working environment in the occupation's history: the file room disappeared, paper charts became screen interfaces, and the coding workflow moved from physical to electronic. Many specialists found the transition difficult; some coding productivity fell 20-50% in the months immediately after EHR implementation as coders adapted from paper-based chart navigation to electronic systems with different structures.
Effect on the workEHR adoption initially created a wave of implementation and training demand for health IT workers; medical records specialists who understood both the clinical content of records and the new software interfaces became valuable in implementation projects. Over the medium term, EHR systems enabled remote work for coders, expanding the labor pool and moderating wages for some coding roles.
Electronic recordDigital charting ICD-10-CM/PCS transition (implementation date: October 1, 2015)
On October 1, 2015, the United States replaced ICD-9-CM with ICD-10-CM/PCS for all HIPAA-covered entities, expanding the code set from roughly 14,000 diagnosis codes to approximately 68,000. The transition had been delayed twice (from 2013 and 2014 target dates) due to industry concern about cost and productivity disruption. When it finally arrived, the disruption was real: average coding time per record rose from pre-implementation baselines and productivity fell roughly 20% in the first months, with coders not returning to ICD-9-CM baseline efficiency until approximately eight months post-transition. The ICD-10 transition simultaneously demanded more from human coders (deeper clinical knowledge to navigate the expanded code set) and accelerated investment in computer-assisted coding tools that could suggest codes from clinical text, the forerunner of today's AI coding platforms.
Effect on the workThe ICD-10 transition created a short-term surge in demand for certified coders and training programs. It also accelerated the shift toward specialization: coders who mastered a specific service line (orthopedics, oncology, cardiology) commanded premiums, while generalist coders faced more pressure from computer-assisted coding tools.
Work toolChanging equipment AI-powered coding and NLP revenue cycle tools (autonomous coding, computer-assisted coding at scale)
Natural language processing systems that automatically suggest or assign ICD-10 and CPT codes from clinical documentation moved from pilot projects to mainstream adoption between 2020 and 2025. The AI in Medical Coding market was valued at approximately $2.4 billion in 2023, growing at roughly 13-16% annually. Hospitals using these tools reported productivity gains of 40-50% per coder and reductions in "discharged not final billed" backlogs. For the medical records specialist, this is the most significant technological threat since the DRG era created the high-complexity coding role: if NLP can assign codes autonomously, the specialist's task list contracts toward review, audit, appeals, and the edge cases that the model cannot handle confidently. Whether this generates workforce displacement or productivity amplification depends on whether healthcare organizations treat the technology as a headcount-reduction lever or as a way to do more coding work with the same staff.
Effect on the workThe BLS projects 7.1% employment growth for 29-2072 through 2034, suggesting the official forecast is that AI coding tools will augment rather than displace the workforce over the medium term, consistent with growing healthcare utilization from an aging population offsetting efficiency gains from automation.
Work toolChanging equipment
What credible sources project
Scrub the slider past now to anchor each scenario on the scrubber. The spread is the range of futures credible sources project for this role.
What's shifting in the work right now
The historical view above shows how this role has moved. This is the present-day detail: which AI tools are picking up which tasks, where the edge still is, and the natural directions this work can grow.
What's changing in your day
Three parts of your work where AI is already doing real lifting, and what stays yours.
AI is sitting alongside you hereReview and validate AI-suggested ICD-10-CM/PCS and CPT codes generated by autonomous coding platforms (Solventum 360 Encompass, AKASA Medical Coding) — accepting high-confidence suggestions on qualified encounters, correcting mismatched codes on flagged charts, and documenting rationale for overrides to build feedback loops that improve model accuracy.
Review and validate AI-suggested ICD-10-CM/PCS and CPT codes generated by autonomous coding platforms (Solventum 360 Encompass, AKASA Medical Coding) — accepting high-confidence suggestions on qualified encounters, correcting mismatched codes on flagged charts, and documenting rationale for overrides to build feedback loops that improve model accuracy.[3],[4],[9]
Shift from initial code assignment to expert audit: develop fluency in reading confidence scores and audit trails that autonomous systems output, and build a disciplined override-documentation practice so your corrections actively improve model performance over time.
AI is sitting alongside you hereMaintain EHR data integrity and patient record quality — reviewing records for incomplete documentation, scanning or migrating paper records into electronic formats, resolving patient identity-matching errors (duplicate MRNs), and enforcing data governance standards that downstream AI coding and analytics tools depend on for reliable input.
Maintain EHR data integrity and patient record quality — reviewing records for incomplete documentation, scanning or migrating paper records into electronic formats, resolving patient identity-matching errors (duplicate MRNs), and enforcing data governance standards that downstream AI coding and analytics tools depend on for reliable input.[6],[1]
Data governance and EHR integrity is becoming a more prominent function as health systems deploy AI tools that are only as accurate as the documentation they ingest. Develop skills in health data literacy, master patient identity management tools, and position yourself as the guardian of data quality that revenue cycle and AI platforms depend on.
AI is sitting alongside you hereConduct clinical documentation improvement (CDI) review — scanning inpatient charts using Iodine Software (Waystar) AI-prioritized worklists for documentation gaps before physician query, validating AI-identified opportunities for more specific diagnosis capture, and issuing compliant physician queries to clarify diagnoses that affect DRG assignment, quality metrics, or risk scores.
Conduct clinical documentation improvement (CDI) review — scanning inpatient charts using Iodine Software (Waystar) AI-prioritized worklists for documentation gaps before physician query, validating AI-identified opportunities for more specific diagnosis capture, and issuing compliant physician queries to clarify diagnoses that affect DRG assignment, quality metrics, or risk scores.[5],[10],[11]
CDI is the growth track within HIM — it sits at the intersection of clinical, coding, and financial domains. Master query compliance standards (AHIMA/ACDIS Practice Brief on Physician Queries), learn risk-adjustment methodologies (HCC, APR-DRG), and build clinical vocabulary depth so you can formulate queries that physicians actually answer.
Where this role is heading
Natural next steps for someone with your foundation: not exits, evolutions.
Compensation and Benefits Managers
Medical Records Specialists with strong health data literacy — coding data quality, HCC risk-adjustment analytics, quality measure reporting (HEDIS, MIPS, Star Ratings) — are positioned to move into health data analytics or informatics roles. As AI coding platforms generate large volumes of structured claims and CDI data, health systems need analysts who understand both the clinical coding provenance and the analytical downstream. This pivot requires building data skills (SQL, Tableau, Python) and earning a health informatics credential, but the domain knowledge from HIM is a significant differentiator that pure data analysts lack.
- · Health data analytics: SQL for EHR and claims data, Tableau or Power BI for population health dashboards
- · Health informatics credentials: RHIA with informatics focus or graduate certificate in health informatics (AMIA 10×10 program)
- · Risk adjustment and value-based care analytics: CMS-HCC model v28, Medicare Advantage RADV, HEDIS measure specifications
- · Python or R for clinical data science: pandas for claims data transformation, statistical analysis of coding patterns
- · Interoperability standards: HL7 FHIR, ICD-10 to SNOMED CT mapping, claims data formats (837P, 835 ERA)
See the same long-arc view for your own profession.
Browse the directory by industry, or search by title or SOC code. New roles ship every few weeks. Every profile cites every claim.
Browse all roles