Risk adjustment documentation
HCC documentation and coding review
QuickRCM training documentation describes HCC mapping review, supporting-document review, recapture follow-up and clarification handoffs. These administrative review workflows do not establish a diagnosis or treatment recommendation. Confirm the enabled module, applicable model and reviewer responsibilities for the proposed deployment.
Explore QuickRCM, risk adjustment, QuickCode coding review and QuickAuth prior authorization. These related references do not establish a shared deployment or integration scope.
The review problem
Source documentation, configured model and reviewer decisions can be distributed across records. Identify missing inputs and unresolved questions before finalization.
A documented review approach
Inspect the suggested mapping alongside source material, route clarification, and verify the intended downstream handoff. These are review tasks, not a guarantee of coding accuracy or clinical benefit.
Documented HCC review workflows
The QuickRCM training manual describes these administrative review workflows. Confirm the enabled module, permissions and applicable model before use.
HCC crosswalk review
The manual describes inspecting mapping, hierarchy and coefficient outputs for the configured model. Verify the program and payment-year context before use.
Human review
Review the source documentation and suggested mapping; record acceptance, modification or rejection through the authorized review workflow.
Recapture follow-up
Review prior-period gaps and assign follow-up; a previous diagnosis or a missing HCC does not establish a current diagnosis.
Submission preparation
Where configured, review the cohort and prepare the required export or handoff. Verify program, format and window requirements and acknowledgement separately.
Documentation and coding checks
Review documentation and applicable coding guidance, resolve conflicts, and request clinician clarification where needed.
Model and demographic configuration
Verify demographic and status inputs and the configured model; investigate stale source data or a model mismatch before finalizing a result.
Clarification handoff
Route unclear documentation to the appropriate clinician and review the returned clarification before completing the coding workflow.
Documentation describes a workflow; it is not a release-status approval, clinical-validation study or customer outcome guarantee.
A documented review sequence
Confirm these steps and permissions for the selected module; this is not a deployment or clinical-outcome promise.
Confirm context
Confirm the patient and encounter, available documentation, authorized connector and relevant model and program.
Review mappings
Inspect the configured crosswalk and hierarchy alongside the supporting record. Investigate missing inputs or mismatches.
Resolve questions
An authorized reviewer accepts, modifies or rejects the suggested mapping. Route unclear clinical documentation for clarification.
Verify handoff
Inspect finalized output and the actual downstream acknowledgement where configured. Preparing an export is not successful transmission.
Evaluation priorities
Agree on what the review must establish before evaluating a proposed deployment.
Supporting-record completeness
Identify which encounter notes, status fields and coding references are needed for the review. Record missing inputs rather than treating them as negative findings.
Review and clarification ownership
Agree who may review mappings, request clinical clarification and finalize the result. Document unresolved questions before handoff.
Handoff verification
Define the expected output, destination and acknowledgement. Evaluate the proposed workflow against your own baseline and acceptance criteria.
Documented review steps to confirm
The training manual describes these review tasks. Confirm the enabled workflow and available records for your deployment.
Inspect
- Review the source encounter and available documentation.
- Check the configured HCC mapping, hierarchy and model context.
Review
- Record acceptance, modification or rejection through the authorized workflow.
- Check the supporting rationale rather than treating a suggestion as a confirmed diagnosis.
Clarify
- Identify unresolved documentation questions.
- Assign the appropriate clinician or reviewer and review the response.
Follow through
- Review the finalized result and available action history.
- Confirm the configured export or handoff and its downstream acknowledgement.
Integration scoping questions
The EHR-integration manual describes configuration and conflict review. It does not verify every connector, resource or clinical application.
Source resources
Which adapter, EHR version and source resources are available for this workflow? Confirm field coverage and missing-data handling.
Authorized direction
Which reads or writes are authorized? Confirm user permissions and reviewer approval before any configured writeback.
Mapping and conflicts
How will field mapping, record conflicts and stale data be reviewed? Identify the owner of unresolved mappings.
Acknowledgement and fallback
How will the team verify the destination accepted a handoff? Agree on investigation and fallback steps when no acknowledgement is returned.
Bring these items to a workflow review
These are planning inputs, not customer testimonials or measured results.
Process outline
Bring a de-identified workflow outline and a list of missing inputs. Do not send patient information through a public demo request.
Reviewer roles
Identify coding reviewers, clinical clarification owners and the person authorized to finalize a handoff.
Model and program scope
Specify the intended program, payment year, service-date context and configuration to review.
Connection and evaluation criteria
List connector constraints, downstream destinations and the acceptance criteria you want to evaluate.
Security review topics
Confirm the requirements and evidence for the proposed service before sharing protected information.
Data flow and retention
- Request the proposed data-flow and hosting-region scope.
- Confirm retention, deletion and permitted uses for the selected service.
Access and reviewer roles
- Review authentication and access requirements for your team.
- Confirm reviewer permissions, available logging and approval responsibilities.
Documentation and contract scope
- Request applicable architecture, audit and contractual documents.
- Verify the covered service, reporting period and any limitations before relying on them.
A documentation request is not confirmation of certification, controls or audit coverage.
Security documentation and reviewRequest a scoped proposal
Discuss these topics with the team. These are scoping questions, not published plans, included capabilities or service-level commitments.
Workflow and users
- Intended review tasks and user roles
- Program, model and documentation inputs
Integration and permissions
- Connector versions, resources and direction
- Access approvals and downstream destinations
Review and implementation
- Clarification and finalization responsibilities
- Evaluation criteria, dependencies and proposed schedule
HCC review scope: frequently asked questions
Documentation, review responsibilities and deployment questions.
What does this page cover?
This page describes HCC administrative and coding-review workflows documented in the QuickRCM training manual. It does not establish clinical diagnosis or treatment functionality, release status or measured customer results.
How should suggested mappings be reviewed?
Review the supporting documentation, configured model and applicable program with an authorized reviewer. Record acceptance, modification or rejection and request clinician clarification for unclear or unsupported conditions.
What does a recapture gap mean?
A recapture gap is a candidate for follow-up, not proof that a prior condition remains present. Review current documentation and resolve clinical questions before finalizing a coding result.
Which model applies?
Confirm the program, payment year, service-date context and configured module before use. Model requirements can differ across programs, including PACE and non-PACE Medicare Advantage. External policy guidance does not establish that a particular QuickIntell deployment implements a model.
How are coding conflicts handled?
Review the source documentation and the official coding guidance applicable to the service date. Do not treat simplified training-manual rules as universal coding policy. Resolve conflicting or unclear documentation with the appropriate clinician before finalization.
Can output be sent directly?
Preparing or exporting output and successfully transmitting it are separate steps. Confirm the enabled integration, accepted program-specific format and submission window, authorization to send, and the actual receipt or acknowledgement. Documentation alone does not establish a live connection.
Are sepsis, AKI, behavioral-health or pediatric pathways available?
Current sepsis, acute kidney injury (AKI), behavioral-health and pediatric pathway availability is not established by the documentation reviewed for this page. Request an owner-approved version, intended use and rollout scope before relying on a clinical pathway. No GA, pilot or roadmap status is assigned here.
What must be confirmed for an EHR connection?
Confirm the adapter, EHR version, resources, read and write permissions, mapping, conflict handling and fallback process. Verify the actual downstream acknowledgement where a handoff is configured; an integration reference is not proof of every connector or capability.
What outcomes or deployment timeline should be expected?
No universal performance result or go-live period is established here. Agree on the workflow scope, baseline, evaluation criteria, dependencies and proposed schedule with the responsible team. Documentation targets and example scenarios are not measured customer results.
How are security requirements reviewed?
Request the applicable architecture, data-processing, retention, hosting-region, contract and audit documents. Confirm their scope, reporting period and availability for the proposed service; do not infer certification or control coverage from marketing badges.
Plan an HCC review workflow walkthrough
Discuss the documentation, reviewer roles, configuration and evidence needed to evaluate your proposed workflow.
Use a de-identified process outline for the discussion. Do not include patient information in a public demo request.