HealthcareFree to read online

Health Information Management and Medical Records Explained

Name: Health Information Management and Medical Records Explained
Availability: InStock
Author: Dr. Kenji Yamamoto

Accuracy, privacy, coding and data quality in the patient record

This reference explains how health information management keeps patient records accurate, private, available and useful. It covers the record itself, clinical coding and classification, privacy and release rules, data quality measurement, the move to electronic records, analytics, workforce roles and the everyday methods professionals use to keep health data trustworthy from capture to retention and secondary use.

Dr. Kenji Yamamoto, Academic Expert, Healthcare
19 min read
25 pages

Start reading

What you will learn

Describe what a health record contains and why its accuracy matters
Explain the purpose of clinical coding and classification systems
Apply core privacy and release principles to routine record decisions
Measure data quality using completeness, timeliness, consistency and validity
Recognize common documentation mistakes and the methods that prevent them

vaayaa Guide

vaayaa

Healthcare · Reference Guide

Health Information Management and Medical Records Explained

Accuracy, privacy, coding and data quality in the patient record

Dr. Kenji YamamotoAcademic Expert, Healthcare

Orientation

001

What Health Information Management Is

Health information management is the discipline that looks after patient information from the moment it is created to the moment it is finally retired. It is concerned with whether records are accurate, whether they can be found when needed, whether they are kept private, and whether the information inside them can be used for care, payment, planning and research. The people who do this work sit between clinicians, administrators, insurers and patients, and they make sure the record behaves as a trustworthy source of truth.

The discipline covers far more than filing. Professionals handle patient identification, consent documentation, indexing, storage, scanning, release of information, coding of diagnoses and procedures, and the measurement of how well the record supports decisions. In many settings the same team also supports disease registries and quality reporting, so their work reaches well beyond a single patient encounter.

Health information management keeps patient data accurate, private, available and useful across its whole life.

Recognized qualifications in this field typically prepare learners for roles such as medical records assistant, health information technologist and health information management professional. Training usually combines classroom study with supervised practice in a real records department, and it is assessed against competency statements that describe what a competent worker must be able to do.

Think of the field as the custodian of a living asset. A record that is incomplete, late or wrongly coded is not a small clerical fault; it can affect treatment, reimbursement and public health statistics. Understanding this from the start shapes every later decision in the discipline.

Accuracy 30%
Privacy 25%
Availability 25%
Use 20%

Core responsibilities of the discipline (Illustrative)

Orientation

002

Where the Field Meets Other Work

Health information management sits at the overlap of three bodies of knowledge. The first is clinical practice, because the record is written by clinicians and must reflect what was actually done for the patient. The second is information technology, because most records now live in electronic systems that must be configured, secured and maintained. The third is law and administration, because records must meet privacy duties, retention rules and the requirements of payers and regulators.

A professional in the field needs enough clinical literacy to read a discharge summary and recognize a missing procedure, enough technical skill to understand how a system stores and retrieves data, and enough knowledge of rules to decide what may be released to whom. No single background covers all three, which is why the discipline values people who can translate between groups.

The field draws on clinical practice, information technology and legal rules at the same time.

This overlap explains why the work is so varied. A question about a missing consent form may be a legal issue, a systems issue and a clinical documentation issue at once. Learning to identify which lens applies first saves time and produces better solutions.

As you read the rest of this ebook, keep this three-way overlap in mind. Many of the concepts that follow are simply the places where these fields meet in practice.

Clinical

Technology

Law

Three bodies of knowledge overlap

Orientation

003

How the Profession Is Structured

The profession is organized in layers. At the base are technicians and assistants who handle the daily flow of records: registration, file preparation, indexing, scanning and release requests. Above them are technologists and coders who assign classification codes, check documentation and produce reports. At the top are managers and specialists who set policy, select systems, lead audits and oversee privacy programs.

Each layer depends on the one below it. Accurate codes depend on complete records, and complete records depend on careful registration and filing. Managers can only design sensible policies when they understand what actually happens at the desk and in the coding queue. Good organizations keep communication flowing up and down these layers.

Entry roles feed the quality and management levels above them, so each layer depends on the one below.

Career progression usually follows this structure, moving from a supervised entry role toward responsibility for quality, systems or compliance. Credentials recognized in a jurisdiction often mark the transition between layers, and each level asks for a broader understanding of how data supports care.

Understanding the pyramid helps a newcomer see where their current task fits and what the next level will require.

Policy leadership

Systems compliance

Coding technologist

Records assistance

Layers of the profession, top to bottom

Orientation

004

The Record Life Cycle

Every piece of health information passes through a repeating cycle. It is captured at the point of care, verified for completeness, stored and indexed, used for care and administration, released when authorized, and eventually retained or disposed of under a schedule. Each stage can introduce errors, so the cycle is managed as a whole rather than stage by stage.

The cycle has a useful property: findings from later stages feed back into earlier ones. If coders repeatedly find that a procedure is not documented, the feedback goes to clinicians and template designers. If release requests are frequently incomplete, the intake process is revised. The record improves when the loop is closed.

Records move through a repeating cycle of capture, verification, storage, use, release and retention.

Professionals therefore think in terms of review rather than one-time checks. They ask whether a process works across the whole cycle and whether the people in each stage have what they need to succeed. This habit distinguishes a managed record system from a collection of files.

The cycle is also the frame for many of the methods later in this ebook, which target specific stages of the loop.

Capture

Verify

Store

Use

The record cycle repeats and feeds back

Core Concepts

005

Defining the Health Record

A health record is the collection of documented information about an individual's care. It typically includes identifying details, consent, histories, examination findings, orders, test results, medication records, progress notes, procedure reports, discharge summaries and correspondence. It may be held in paper form, in an electronic system, or in a hybrid of both.

The record has a dual purpose. It guides the care of the current patient and it serves as evidence of what happened. Clinicians rely on it to coordinate treatment across shifts and specialties. Payers, auditors and courts may later rely on it to judge whether care was delivered and documented properly.

A health record must be clear, timely and attributable because many different people will rely on it.

Because the record serves so many readers, its content must be clear, timely and attributable to a specific author. Entries are expected to show who wrote them and when, and corrections are handled by a formal process rather than by overwriting history.

A practical test for any record is whether a competent colleague, reading it later without the author present, could understand what was done and why.

Document care

Attribute author

Correct formally

Review clarity

Steps for keeping records clear

Core Concepts

006

Identifying Patients Correctly

Patient identification is the foundation of every record. If a result or note is filed under the wrong person, the consequences can be serious, from repeated tests to wrong treatment. For this reason, the registration process collects demographic details and checks them against source documents, and identifiers are used consistently across systems.

Matching patient data with related systems is a routine but careful task. Civil registry details, insurance information and existing record numbers must be compared, and discrepancies resolved before a new file is opened. Duplicate records must be detected and merged under controlled procedures.

Correct patient identification is the foundation, because one misfiled result can affect the wrong person.

Consent documentation is also gathered at this stage, and it must be linked to the correct patient and encounter. Files are then numbered and assigned to the department responsible for care, with coordination between outpatient, inpatient and emergency settings.

A small registration error often remains invisible for years, so disciplined identification is one of the most valuable habits a professional can build.

Collect

Check

Match

File

Registration steps that protect identity

Core Concepts

007

Measuring Record Completeness

Completeness is one of the core dimensions of data quality. A record is complete when every required element for an encounter is present, signed and dated. Incomplete records weaken care, slow coding, delay billing and expose organizations to legal risk. Professionals measure completeness rather than assuming it.

A typical completeness review checks each encounter against a defined list of required documents, such as history, examination, orders, consent, progress notes and discharge summary. The result is expressed as a proportion of encounters that meet the standard, and the gaps are tracked by department and by document type.

Completeness is measured against a defined checklist so that gaps can be counted and addressed.

The chart below shows an illustrative pattern of missing elements in a review. The numbers are examples to show how a gap analysis is presented, not findings from a real facility. Such a chart helps teams decide where to focus their effort.

Measurement changes behavior. Once a team sees where gaps cluster, it can address the cause, whether that is a template problem, a training need or a workflow bottleneck.

Consent

Discharge

Progress

Signatures

Illustrative share of encounters missing each element (Illustrative)

Core Concepts

008

Timeliness and the Life of a Record

Timeliness asks whether documentation is entered when it should be. Entries made long after an event may omit details that were clear at the time, and they lack credibility when read later. Good practice is to complete notes at or near the point of care, supported by workflows that make this easy.

The timeline of a typical record shows several moments that matter. Documentation is started during the encounter, completed before handover, signed by the responsible clinician, coded after discharge, and finally released or archived. Delays at any stage push the whole chain back.

Timely documentation reflects real events, while late entries risk losing important detail.

Professionals track turnaround times for each step. A coding backlog or a delay in signing discharge summaries is visible in these measures, and it can be addressed with clear deadlines and reminders.

Timeliness is not the same as speed at any cost. A rushed entry that is inaccurate is worse than a timely one that is correct, so measures are read together.

Encounter

Note

Sign

Code

Release

Consistency and Validity Checks

Consistency means that the information in a record agrees with itself and with related records. A diagnosis in the discharge summary should match the diagnosis on the coded claim, and medication lists should not contradict each other. Contradictions weaken the record and make both clinical and legal review harder.

Validity asks whether values fall within accepted ranges and use accepted codes. A date of birth in the future or a code that does not exist in the classification is a validity error. Systems can enforce many of these rules automatically, but professionals still review exceptions.

Consistent, valid data agrees with itself and follows accepted rules for values and codes.

A simple matrix helps teams rate each record on these dimensions. Ratings from one to three indicate how well each area performs, and the pattern points to where interventions should be targeted. The matrix below is illustrative, showing how ratings are arranged across the dimensions.

Consistency and validity are often checked together, because an invalid code usually produces an inconsistent claim. A combined check catches more problems than either alone.

	Consistency	Validity	Timeliness
Inpatient	●●	●●●	●●
Outpatient	●●●	●●	●●●
Emergency	●	●●	●●

Illustrative ratings by record area

Core Concepts

010

Core Concepts at a Glance

Several ideas recur throughout the discipline. Data quality rests on completeness, timeliness, consistency and validity. Privacy rests on limiting access to what is needed and recording who saw what. Coding rests on mapping narrative documentation to standard classifications. Governance rests on policies that assign responsibility for each of these.

These concepts connect in a web rather than a list. A gap in documentation affects coding, which affects statistics, which affects planning. A privacy breach affects trust, which affects what patients are willing to disclose. Thinking in connections helps professionals predict the effects of a change before they make it.

Data quality, privacy, coding and governance are linked, so a change in one affects the others.

A mind map is a useful way to hold the whole picture. It places the central idea of managed health information at the center and arranges the main concerns a round it, so that each new topic in this ebook has a clear place to attach.

Returning to this map as you read the later pages will help you see how methods and decisions relate to the foundations described here.

Managed
Records

Quality

Privacy

Coding

Governance

Analytics

Retention

Central ideas of managed health information

Methods

011

Choosing a Classification

Classification systems translate clinical language into standard codes. A diagnosis written in narrative form is assigned a code from an agreed list, which allows records to be counted, compared and reimbursed consistently. The best-known international system for diseases is the International Classification of Diseases, which is updated periodically and used for statistics and coding.

Professionals must use the current version and the guidelines that accompany it. Assigning codes to documents should follow organizational policy, and codes must reflect what the record actually says rather than what a coder assumes. Procedures are coded with their own systems, and the coder must link them to the documented service.

Codes must reflect what the record documents, using the current classification and its guidelines.

Choosing the right code is a skill built through study and repeated practice. Coders read the whole encounter, identify the principal reason for care, and apply the rules for sequencing and for secondary conditions.

When the record is unclear, the correct action is to query the clinician, not to guess. A good query is specific, non-leading and documented.

Direct 55%
Query 30%
Review 15%

Share of coding decisions by method (Illustrative)

Methods

012

Coding Methods and Checks

A common coding workflow begins with reviewing the full encounter, then assigning diagnosis codes, then assigning procedure codes, and finally checking the result against guidelines and against the documentation. Each step includes a check so that errors are caught before the record leaves the coding department.

Two overlapping sources of knowledge are needed for accurate coding: knowledge of the classification and knowledge of clinical practice. The classification tells the coder what the codes mean and how to sequence them. Clinical knowledge helps the coder recognize what the documentation is describing, even when the terms are informal.

Accurate coding uses a repeating review process, supported by audits that catch and correct errors.

Professionals also use audits to check the work of others. A sample of coded records is reviewed independently, and disagreements are discussed and used to refine guidance. Accuracy rates are tracked over time.

These methods make coding a process rather than a personal skill, which is essential when many people contribute to the same records.

Coding
rules

Clinical
practice

Audits

Three inputs that shape accurate coding

Methods

013

Building a Records Pyramid of Skills

Competence in records work can be arranged as a pyramid of skills. The base is accurate handling: correct filing, numbering, scanning and identification. Above it sits documentation knowledge, which means understanding what a complete record contains. Next comes coding and classification, and at the top sits analysis and governance, where a professional designs and checks the whole system.

Each level depends on the level beneath it. An analyst cannot trust statistics built on careless filing, and a coder cannot produce reliable codes from incomplete records. Training that builds the base first tends to produce workers who grow steadily upward.

Skills build upward, from accurate handling to documentation, then coding, then analysis and governance.

Competency frameworks in this field describe the same progression. They list knowledge, skills and attitudes for each area and describe how each is assessed, often through observation in a working environment.

When planning your own development, identify which level you are working at and what the level above requires. The pyramid gives a clear next step.

Analysis governance

Coding classification

Documentation knowledge

Accurate handling

Levels of records competence, top to bottom

Methods

014

A Cycle for Continuous Improvement

Quality improvement in records work follows a cycle. The team assesses the current state, plans a change, implements it on a limited basis, and reviews the results. If the change worked, it is adopted and monitored; if not, the cycle begins again with new information.

This approach suits records problems because they are rarely solved by a single fix. A rise in missing consents might be addressed by a new form, then by staff training, then by a daily check, and each step is measured before the next is added.

Records improvement runs as a loop of assessing, planning, treating and reviewing, repeated until results hold.

Teams that use the cycle keep a simple record of each round: the problem, the change, the result and the decision taken. This record becomes institutional memory and prevents repeating failed attempts.

The cycle also protects against premature conclusions. A review step asks whether the measured change is real or whether it reflects a temporary effect of the project itself.

Assess

Plan

Treat

Review

Improvement loop for records problems

Methods

015

Release of Information Procedures

Release of information is the process by which requests for copies of records are received, verified, processed and documented. A request might come from the patient, from another treating provider, from an insurer or from a legal representative. Each requester has different authority, and the process must confirm that authority before any information leaves the organization.

A standard workflow begins with intake, where the request, the requester's identity and their authority are recorded. Next the scope of the request is defined, and the relevant records are gathered. Before release, the content is checked for completeness and for information that must be with held or redacted under applicable rules.

Each release requires verified authority, a defined scope, a completeness check and a documented record.

The release is documented, including what was sent, to whom and when. Records of releases are themselves part of the audit trail, and they must be retained with the same care as the health record.

Errors in this process are costly, so many organizations use checklists and second reviews for sensitive requests.

Intake

Verify

Gather

Redact

Release

Standard release workflow

Methods

016

Access Control in Practice

Access control decides who may see which parts of a record and for what purpose. Good practice limits access to what each role needs, a principle often described as minimum necessary. Clinicians may see records for patients in their care, while administrative staff may see only the data needed for their task.

Access is controlled through a chain of decisions. A user is authenticated, assigned a role, and granted permissions. The system records each access event so that later reviews can show who viewed which record and when. Audit logs are one of the most useful tools for detecting inappropriate access.

Access should be limited to the minimum needed for each role and every access event should be logged.

Access rules must be applied consistently. Exceptions, such as access to a record of a colleague or of a public figure, should be treated as higher risk and reviewed. Training helps staff understand why these rules matter and how to report concerns.

Privacy is therefore less about locking files and more about governing a steady flow of legitimate access.

Authenticate

Assign role

Grant access

Log event

Access decisions in order

Applications

017

Privacy Duties and Consent

Patients have an expectation that information shared in confidence will be protected and used only for appropriate purposes. Privacy rules set out the obligations of organizations that hold records, including limits on use and disclosure, duties to safeguard information, and rights for patients to see and request corrections to their own records.

Consent is a related concept. Documentation of consent records what the patient agreed to and under what conditions, and it must be linked to the correct encounter. Where consent is withdrawn or limited, systems must reflect that decision so that staff act accordingly.

Privacy duties govern use, disclosure and safeguarding, and consent must be documented against the right encounter.

Privacy breaches are treated seriously. Organizations are expected to detect, investigate and report incidents, and to take steps to prevent recurrence. Professionals who handle records must know how to recognize and escalate a potential breach.

This topic is covered here for its role in records practice; the details of any particular legal regime are determined by the jurisdiction in which a record is held.

Misfile

Access

Release

Share of incidents by type, illustrative (Illustrative)

Applications

018

The Path to Electronic Records

Many organizations have moved from paper records to electronic systems, and most are now in a hybrid state. The transition raises questions about which records are authoritative, how paper is scanned, how historical information is migrated, and how staff are trained to work in new systems.

A typical transition unfolds in stages. Planning and system selection come first, followed by configuration, testing, data migration, training and a period of parallel running. After go-live, the team monitors performance and corrects problems. Each stage carries risk, and the path is rarely linear.

Electronic transition moves through planning, configuration, migration, training and monitoring, with validation at each step.

Scanning paper records is a not able part of the work. Scanned documents must be indexed correctly, checked for legibility and completeness, and linked to the right patient. Once scanning is complete, retention rules govern what happens to the originals.

Migration requires careful mapping of data fields, and it is wise to validate samples of migrated records against the source before the old system is retired.

Plan

Configure

Migrate

Train

Monitor

Stages of an electronic records transition

Applications

019

Choosing Between Competing Options

When an organization considers new systems or processes, it compares options against criteria that matter to records quality. Typical criteria include how well the option supports completeness, how easily staff can use it, how well it protects privacy, and how it integrates with existing systems.

A matrix helps structure this comparison. Each option is rated on each criterion, and the ratings are reviewed together rather than in isolation. The example below is illustrative, showing how three options might be rated on three criteria with a rating of one to three for each.

A structured comparison of options against records criteria makes system decisions clearer and easier to defend.

Decisions also weigh cost and risk, and they should involve the staff who will use the system daily. Their feedback often reveals problems that a demonstration does not show.

A clear, documented comparison makes the final choice easier to defend and easier to revisit later.

	Completeness	Usability	Privacy
Option A	●●●	●●	●●●
Option B	●●	●●●	●●
Option C	●	●●	●●●

Illustrative ratings of three options

Applications

020

Analytics and Secondary Use

Once records are accurate and well organized, they can be used for purposes beyond the individual encounter. Secondary use includes planning, quality reporting, disease surveillance, research and administration. These uses depend entirely on the quality of the underlying data, which is why records management and analytics are closely linked.

Disease registries are a common example. A registry is a structured database of patients with a given condition, built from clinical records and maintained over time. Maintaining a registry requires consistent coding, careful data entry and ongoing checks for completeness.

Secondary use such as registries and reporting is only as reliable as the underlying records.

Analytics teams draw on several linked themes. Data must be defined through dictionaries, sources must be understood, and results must be checked before they are published. Privacy applies to analytics too, often through de-identification and aggregation.

Reliable analysis is a product of disciplined records work, so analysts and records staff share responsibility for the final results.

Disease
Registry

Coding

Quality

Privacy

Dictionary

Reporting

Research

Themes linked to a disease registry

Applications

021

Careers in Health Information

Careers in health information span many settings, including hospitals, physician practices, clinics, public health departments, insurers and software organizations. Roles range from records assistant to health information technologist, coder, data quality specialist, analyst and manager.

Career paths are varied. Many professionals begin in clinical, coding, revenue or operations roles and move into analytics or management as their data skills grow. A career record often shows movement across functional areas rather than a single straight line.

Health information careers range from records assistance to analytics and management, often across several functions.

Credentials and recognized qualifications help define entry points and progression, and the specific requirements depend on the jurisdiction and the employer. Continuing education keeps knowledge current as classifications, rules and technologies change.

Anyone considering this field should review the competency expectations for the role they want and plan a path that builds the skills in the order described throughout this ebook.

Records 35%
Coding 25%
Analytics 20%
Management 20%

Share of roles by function, illustrative (Illustrative)

Practice and Review

022

Common Mistakes in Documentation

Professionals repeatedly encounter a small set of documentation mistakes. Inconsistent or incomplete entries weaken the record. Delayed entries lose detail. Overreliance on prefilled templates or copied text creates inaccurate and repetitive content. Unclear language and nonstandard abbreviations slow readers and invite misinterpretation.

These mistakes have predictable consequences. Missing consents create ethical and legal problems, and omitted progress details undermine continuity of care. Poor handwriting and vague treatment plans reduce the value of the record for everyone who reads it later.

Most documentation problems come from a small set of repeatable habits that can be checked and corrected.

The cure is partly individual, through clear writing and timely entry, and partly organizational, through workflows and templates designed to support accuracy rather than to speed completion at any cost. Audit findings are most useful when they lead to changes in these systems.

Recognizing the mistakes is the first step toward preventing them, and a practical checklist is a simple way to build that habit.

Incomplete
entries

Delayed
entries

Copied
text

Common documentation errors overlap

Practice and Review

023

Methods That Prevent Errors

Preventing records errors depends on a combination of methods. Standard templates should prompt for required elements without forcing staff to copy text. Verification steps should confirm identity before data is entered. Peer review and audits should sample completed work. Training should explain both the rules and the reasons behind them.

Layered defenses work better than any single safeguard. A system that flags missing fields, a coder who queries uncertain documentation, and an auditor who samples finished records together catch far more errors than any one of them alone.

Layered safeguards such as prompts, verification, audits and root cause review prevent more errors than any single control.

Professionals also learn from the errors that do occur. A root cause review asks why the error happened and what process allowed it, and the answer leads to a change in the process rather than blame on an individual.

These methods form a practical toolkit that can be adapted to any setting, from a small clinic to a large hospital system.

Training

Audits

Verification

Templates

Layered safeguards that prevent errors

Practice and Review

024

Review and Next Steps

This ebook has moved from orientation to core concepts, methods, applications and common mistakes. The main ideas to remember are that health information management governs the full life of a record, that data quality rests on completeness, timeliness, consistency and validity, that coding converts documentation into standard classifications, and that privacy and release rules protect patients while allowing legitimate use.

Ordered thinking helps in practice. Begin with identification and completeness, then check coding and validity, then consider privacy and release, and finally look at analysis and governance. Use the improvement cycle to test changes, and let measurement guide decisions.

Remember the record cycle, the four dimensions of data quality, and the layered methods that keep records trustworthy.

For next steps, review the competency statements for the role you intend to hold, compare them with your current knowledge, and plan practice in the areas you find weakest. Consult the current classification guidelines and the privacy rules that apply in your jurisdiction.

The field rewards patience, precision and care, because every record you handle is someone's history.

Measure results

Test change

Decide action

Review process

Improvement cycle for testing changes

References

025

References and Learning Sources

vaayaa References

vaayaa Statistics, vaayaa Sprouter discourses on Health Information Management and Medical Recordshttps://vaayaa.com/sprouter
vaayaa Editorial Team, vaayaa News on Digital Health Operationshttps://vaayaa.com/news
vaayaa Research Desk, vaayaa Sprouter discourses on Community and Public Health Practicehttps://vaayaa.com/sprouter
vaayaa Subject Matter Review, vaayaa News on Medical Imaging and Radiologic Technologyhttps://vaayaa.com/news

Learning Sources

Micro Degree Health Information Management and Medical Recordshttps://vaayaa.com/course/health-information-management-and-medical-records
Micro Degree Digital Health Operationshttps://vaayaa.com/course/digital-health-operations
Micro Degree Community and Public Health Practicehttps://vaayaa.com/course/community-and-public-health-practice
Micro Degree Medical Imaging and Radiologic Technologyhttps://vaayaa.com/course/medical-imaging-and-radiologic-technology
Micro Degree Medical Laboratory Technology and Diagnosticshttps://vaayaa.com/course/medical-laboratory-technology-and-diagnostics

Health Information Management and Medical Records Explained

What you will learn

Contents

What Health Information Management Is

Where the Field Meets Other Work

How the Profession Is Structured

The Record Life Cycle

Defining the Health Record

Identifying Patients Correctly

Measuring Record Completeness

Timeliness and the Life of a Record

Consistency and Validity Checks

Core Concepts at a Glance

Choosing a Classification

Coding Methods and Checks

Building a Records Pyramid of Skills

A Cycle for Continuous Improvement

Release of Information Procedures

Access Control in Practice

Privacy Duties and Consent

The Path to Electronic Records

Choosing Between Competing Options

Analytics and Secondary Use

Careers in Health Information

Common Mistakes in Documentation

Methods That Prevent Errors

Review and Next Steps

References and Learning Sources

vaayaa References

Further Reading

Learning Sources

More in Healthcare

Healthcare Administration Practice: Running the Business of Care

Healthcare Administration and Hospital Management: A Working Guide

Healthcare Quality, Safety and Infection Control Explained

Hematology and Oncology: A Practical Reference