Study guide
Contracting and Outsourcing Governance
RHIA Study Guide Exam
Track your progress as you read
Finished sections get a check mark.
1 Orientation: RHIA Eligibility, Application, Fees, Format, Scoring, and Retakes
1.1 RHIA Purpose and Administrator-Level Scope 1.2 HIM-Only Eligibility Routes 1.3 MyAHIMA Application, Transcripts, and the 120-Day Scheduling Window 1.4 Fees, Format, and Appointment Time 1.5 Passing Score and Score Interpretation 1.6 Retakes, Certification Maintenance, and Current Statistics
2 2023 RHIA Outline, Exam Functionality, Pretest Items, and Study Strategy
2.1 Current 2023 Outline and Why It Controls Study 2.2 Domain Weights and Study-Time Allocation 2.3 Scored Items, Pretest Items, and Answer Discipline 2.4 Navigation, Flagging, Review, and Submit Workflow 2.5 Test Center Day and No-Resource Requirement 2.6 Official Task-Based Study Strategy
3 Data and Information Governance I: Documentation Integrity and Quality Reporting
3.1 Documentation Integrity as Governance 3.2 Complete, Accurate, and Timely Records 3.3 Documentation Standards and Clarification Workflows 3.4 Clinical Data Elements for Quality Reporting 3.5 Data Quality Validation for Reporting 3.6 Governance Committees, Metrics, and Remediation
4 Data and Information Governance II: Data Dictionaries, Retention, MPI, and Policy
4.1 Data Dictionary Standardization 4.2 Documentation and Data Standards 4.3 Data Analysis to Inform Management 4.4 Policies and Procedures for Information Governance 4.5 Retention and Destruction Policies 4.6 Master Patient Index Integrity
5 Compliance I: Access, Use, Disclosure, Patient Rights, ROI, and HIE
5.1 Domain 2 Compliance Decision Frame 5.2 Patient Access and Portal Governance 5.3 Advocacy for Patients and Families 5.4 ROI Intake, Validation, and Scope Control 5.5 Disclosure Documentation and Audit Trails 5.6 HIE and External Access Governance
6 Compliance II: Security, Breach Workflows, Cybersecurity, and Disaster Recovery
6.1 Request Workflow Controls and Escalation 6.2 Breach Protocols from Report to Resolution 6.3 Privacy and Security Initiatives 6.4 Cybersecurity Risks for HIM Leaders 6.5 Disaster Recovery and Downtime Readiness 6.6 Monitoring, Metrics, Tabletops, and Continuous Improvement
7 Data Analytics and Informatics I: EHR Support, Reporting, Databases, and Dashboards
7.1 EHR Support and HIM Administration 7.2 Reporting Lifecycle and Data Requests 7.3 Visualizations, Dashboards, and Executive Views 7.4 Database Management and Data Dictionaries 7.5 Data Mining and Analytics Workflows 7.6 Statistics Validation for Stakeholders
8 Data Analytics and Informatics II: CDI, Workflows, HIE, Integrations, and SDLC
8.1 Focused Documentation Audits for CDI, Quality, and Safety 8.2 CDI Workflows and Query Governance 8.3 Workflow Optimization Through Health Information Technology 8.4 HIE Governance and Exchange Controls 8.5 Software Integrations and Health Information Impact 8.6 Systems Development Life Cycle and HIM Participation
9 Revenue Cycle Management I: Reimbursement, Coding Validation, CDI, and Claims
9.1 Domain 4 Revenue Cycle Management Frame 9.2 Reimbursement Models and Provider Education 9.3 Coding Accuracy Validation Controls 9.4 HHS Documentation Requirements and CDI 9.5 Claims Workflow and Clean-Claim Controls 9.6 CDM, DNFB, and A/R Management
10 Revenue Cycle Management II: Revenue Integrity, Denials, Fraud, and Official Guidelines
10.1 Official Guidelines and Code Assignment 10.2 Groupings and Payment Data Validation 10.3 Revenue Integrity Program Design 10.4 Coding Audits, Monitoring, and Corrective Action 10.5 Denials Management and Appeals 10.6 Fraud Prevention and Compliance Escalation
11 Management and Leadership: Strategy, HR, Work Design, Training, Budgeting, and Projects
Strategy, Goals, and Change Management Contracting and Outsourcing Governance Human Resources, Staffing, and Performance Work Design and Process Improvement Training and Development Budgets, Accreditation, Compliance, and Projects
12 Final RHIA Review: Domain Integration, Exam Week, and Career Next Steps
Integrated Scenario Patterns Across Domains Final Week Domain-Weighted Review Test-Center Day, Functionality, and Pacing Results, Retakes, and RHIA Maintenance RHIA, RHIT, CHDA, CHPS, and CCS Career Map Readiness Checklist and Next-Step Plan
Contracting and Outsourcing Governance
Key Takeaways Explain This Topic AI
Outsourcing PHI work to a vendor requires a HIPAA Business Associate Agreement (BAA) before any access is granted.
An RHIA leader defines scope, service-level agreements (SLAs), reporting, and escalation before work is outsourced.
Vendor performance must be monitored with audit evidence, not informal satisfaction alone.
Outsourcing changes who performs the work but never removes the organization's compliance accountability.
Last updated: June 2026
Contracting Without Losing Control
Contracting and outsourcing help an organization manage volume, gain specialized expertise, or cover staffing gaps. For RHIA purposes, outsourcing is never just a purchasing decision. The HIM leader must protect health information, preserve service quality, define accountability, and ensure vendor work matches organizational policy and law.
The single most-tested compliance anchor here is the Business Associate Agreement (BAA) : under the HIPAA Privacy and Security Rules, any vendor that creates, receives, maintains, or transmits protected health information (PHI) on the organization's behalf is a business associate , and a signed BAA must be in place before PHI access is granted.
Common outsourced HIM functions include release-of-information (ROI) support, document scanning, coding support, transcription services, audit work, and project staffing. You will not memorize a contract template; you will recognize what must be controlled before records, claims, or data-quality tasks move outside the department.
Build the scope and the SLAs
The first step is a clear scope of work : what the vendor performs, what data and systems they access, what standards apply, and what output returns. A vague scope makes performance unmeasurable and risk unmanageable. The second step is a service-level agreement (SLA) that sets measurable thresholds. For coding, the industry benchmark is typically 95% coding accuracy and a 3-to-5-day discharged-not-final-billed (DNFB) turnaround; for ROI, the HIPAA right-of-access standard is 30 days (with one 30-day extension).
The SLA names who reviews vendor work, the audit sample size, and the consequence when performance falls below target.
- Contract control What the RHIA leader must verify
- BAA Signed before PHI access; defines permitted uses, breach reporting, and PHI return/destruction
- Scope Specific services, records, data elements, systems, and excluded work
- Access Minimum-necessary, role-based permissions, and prompt access termination
- Quality SLA Accuracy standard (e.g., 95% coding), audit method, correction, and trend reporting
- Turnaround SLA Defined times for routine, urgent, and exception work (e.g., ROI 30 days)
- Escalation Named contacts, response times, incident/breach reporting, corrective action
- Exit plan Return or destruction of PHI, knowledge transfer, continuity of service
- Worked scenario and traps
A coding vendor hits its turnaround SLA but coding-related denials rise. Speed is not the only measure. A vendor that produces quick charts while increasing denials has not solved the problem, so the RHIA manager reviews quality data, audit findings, and denial trends against the contract, then triggers corrective action. An ROI vendor that answers quickly but mishandles authorization requirements creates a disclosure violation, which is a far higher exposure than a slow queue.
Common traps: assuming the vendor "owns" all compliance risk once the contract is signed (the covered entity retains accountability under HIPAA); granting access before the BAA is executed; measuring only turnaround; and leaving internal staff unclear on which work stays in-house. Strong contracting keeps the organization in control through requirements, audits, reporting, and corrective action. The vendor performs the task; the organization still owns the governance. On the exam, that distinction is the difference between delegation and abandonment.
Make-or-buy and the build vs. outsource decision
Before choosing a vendor, the RHIA leader runs a make-or-buy analysis : compare the fully loaded internal cost (salaries, benefits, software, supervision, downtime risk) against the vendor's price plus the cost of managing the contract. Outsourcing wins when the work is seasonal, requires scarce expertise (such as inpatient coding during an ICD-10 backlog), or when internal capacity cannot scale. Keeping work in-house wins when the function is core, highly sensitive, or so integrated with other workflows that handoffs would multiply errors.
The exam favors the answer that weighs cost, quality, risk, and control rather than chasing the lowest price.
Subcontractors and breach accountability
A frequently tested wrinkle: a business associate may use a subcontractor that also touches PHI. Under the HIPAA Omnibus Rule (2013), that subcontractor is itself a business associate and must sign a BAA with the vendor; liability flows down the chain. If a coding vendor's offshore subcontractor causes a breach, the organization can still face exposure, which is why the BAA must require flow-down agreements and breach notification within defined timelines (HIPAA requires breach notice to the covered entity, then to affected individuals, generally within 60 days of discovery).
- Outsourcing decision factor Favors keeping in-house Favors outsourcing
- Volume pattern Steady, predictable Seasonal or spiking
- Expertise Common, trainable Scarce or specialized
- Sensitivity Highly sensitive PHI Routine, well-bounded
- Integration Tightly coupled handoffs Cleanly separable task
- Cost (fully loaded) Internal cheaper Vendor cheaper net of oversight
- Monitoring as a continuous duty
Vendor governance does not stop at signing. The RHIA leader schedules recurring audits (for example, a monthly coding-accuracy review of a defined chart sample), reviews SLA dashboards, holds quarterly business reviews, and documents corrective-action plans when targets slip. If a vendor repeatedly misses an SLA, the contract's remedies, fee credits, cure periods, and ultimately termination with an orderly transition, come into play.
The exam-correct posture is proactive evidence-based oversight: the organization measures, documents, and acts, treating the vendor relationship as an extension of its own quality and compliance program rather than a problem handed off and forgotten.