TrueCareCost privacy policy

RCM PROJECT POLICIES & OPERATING GUIDELINES

A practical framework for consistent delivery, fair client engagement and protection of TrueCareCost operations

DOCUMENT CONTROL DETAILS
Document ID / Version TCC-RCM-POL-001 / Version 1.0
Policy owner TrueCareCost Healthcare Services – Operations
Applies to Employees, contractors and authorised delivery personnel assigned to RCM engagements
Effective date Upon management approval and internal communication
Review cycle Every 6 months, or sooner if operations, contracts or applicable requirements change
Related documents Master RCM SOP, client-specific SOW, BAA / data-processing terms, process workflows and escalation matrix
Approval authority TrueCareCost authorised management

Purpose and Policy Position

These policies establish the minimum operating rules for TrueCareCost Healthcare Services (TrueCareCost) when delivering revenue cycle management (RCM) services. They support dependable service delivery while protecting against unclear scope, unmanaged workload, avoidable rework, unapproved commitments, security exposure and commercial disputes.

Controls must be proportionate to the service, risk, client environment and contracted volume. Teams must not promise outcomes dependent on payer decisions, clinical judgement, client-supplied information or other external factors.

Order of Precedence

Where documents conflict, the following order applies, subject to applicable law:

  • 1. Applicable law and binding regulatory requirements.
  • 2. Executed Master Services Agreement (MSA), Business Associate Agreement (BAA), data-processing terms and other signed contractual documents.
  • 3. Executed client-specific Statement of Work (SOW), including approved service levels, scope, fees and exclusions.
  • 4. Approved client-specific workflows, security instructions and written change requests.
  • 5. TrueCareCost master SOP and these policies / guidelines.

No internal policy can amend a signed contract. Where a conflict is identified, staff must pause the affected activity where safe to do so and refer it to the Project Lead or authorised management.

Core Policy Rules

  • Work only within approved scope, systems, locations, operating hours and volume assumptions.
  • Do not start production processing until required agreements, access, training, workflow and readiness approvals are in place.
  • Use approved systems and channels for client data and work instructions; record material work and decisions in the agreed system of record.
  • Do not make clinical decisions, alter clinical documentation, invent missing information or select codes unsupported by the record.
  • Do not guarantee claim payment, payer approval, credentialing outcomes, authorisation, reimbursement levels or denial overturns.
  • Raise blockers early. Do not conceal backlogs, errors, missed handoffs or uncertain work status.
  • Additional work, material volume increases and scope changes require written approval before implementation.

Engagement Acceptance and Client Due Diligence

4.1 Acceptance review

Before accepting or expanding an engagement, the Business / Account Lead and Operations Lead assess:

  • Requested service lines and TrueCareCost capability, trained capacity and approved processes.
  • Client specialty, provider and location profile, payer mix, transaction volumes, seasonality and complexity.
  • Required systems, payer portals, clearinghouses, interfaces, remote access and client-side support.
  • Service hours, time zones, turnaround requirements and deadline exposure.
  • Data types, PHI access, security requirements, subcontractor use and contractual safeguards.
  • Pricing model, minimum commitments, volume assumptions, payment terms and implementation effort.
  • Known operational risks, incomplete documentation, historical backlog and client dependencies.

4.2 Right to defer or decline

TrueCareCost may defer commencement, limit the initial pilot or decline work where scope is unclear, safeguards are absent, capacity is unavailable, activity is outside competence or delivery is not reasonably achievable under agreed conditions. The reason and a practical remediation path should be communicated.

4.3 No informal commitments

Only authorised representatives may approve pricing, discounts, service credits, liability commitments, guaranteed targets, contract amendments or additional resources. Delivery personnel must not make such commitments in calls, email or messaging channels.

Scope, Volume and Change Management

  • Each client must have a signed SOW identifying included and excluded services, deliverables, volumes, operating hours, turnaround definitions, client dependencies, fees and assumptions.
  • Measure volume using the unit defined in the SOW (for example, claims, encounters, accounts, providers or transactions). Different work types are not equivalent unless agreed.
  • If actual volumes exceed the agreed baseline or tolerance on a sustained basis, the Project Lead notifies the client and proposes a capacity, timeline or commercial adjustment.
  • Complexity increases, new specialties, payers, locations, systems, reporting or compliance requirements are potential scope changes.
  • Log and assess out-of-scope requests. Start only after written approval, except a documented temporary action jointly authorised to address an urgent operational risk.
  • Urgent client requests may require reprioritisation; explain and record the impact on other work.
Situation Required response
Volume exceeds agreed range Track variance, notify client, estimate capacity impact and agree a revised plan.
New service / specialty Assess competency, workflow, access, training, risk and commercial impact before acceptance.
Faster turnaround requested Check feasibility and dependencies; agree revised target and resource / fee implications in writing.
Repeated incomplete source data Document examples, quantify impact where possible and request client-side corrective action.
Unplanned backlog transfer Inventory and sample the backlog; agree scope, priority, data-quality assumptions and pricing before bulk processing.

Resource, Staffing and Work Allocation

  • Operations allocates work based on approved scope, demonstrated competency, training completion, access rights and workload.
  • Each active work queue must have a named operational owner and backup where practicable.
  • Staff must not use another person's login or share passwords, tokens or multifactor authentication codes.
  • Cross-training is encouraged; independent processing of a new work type requires training and competency confirmation.
  • Manage leave, attrition and temporary absence through handover. Communicate material coverage risks that could affect contracted delivery.
  • Client-specific instructions must be available to the assigned team in a controlled, current location.

Work Intake, Prioritisation and Queue Management

7.1 Accepted intake channels

Work must enter through the client-approved queue, secure portal, approved client system or authorised secure transfer method. Personal email, personal cloud storage and informal messaging are not approved PHI intake channels unless expressly authorised under the applicable security and contractual framework.

7.2 Minimum work record

  • Unique work reference or source-system identifier; date and time received; work type and assigned owner.
  • Priority, due date or filing / authorisation deadline where known.
  • Current status, action history, pending dependency and next action.
  • Submission, payer or clearinghouse reference where applicable.

7.3 Prioritisation

Priority Typical examples Handling guideline
P1 – Time critical Filing deadline at risk, urgent authorisation dependency, critical payer / system issue. Escalate promptly; assign an owner; agree immediate next action.
P2 – High Aged high-value queue, recurring rejection pattern, material client-impacting backlog. Prioritise within daily workload plan and monitor to resolution.
P3 – Standard Routine claims, posting, follow-up and administrative processing. Process in agreed queue order and target.
P4 – Planned Non-urgent clean-up, historical analysis, optional enhancement. Schedule when capacity and scope are approved.

Priority labels do not create a new contractual response time. Applicable targets are those in the SOW or an approved operational plan.

Client Information and Dependency Policy

TrueCareCost relies on the client to provide complete, accurate, current and authorised source information.

  • Do not guess missing patient demographics, insurance details, clinical facts, provider credentials, signatures or medical-necessity information.
  • Where information is missing or inconsistent, place the item in pending status with a clear query and responsible party.
  • Record client-side delays, payer delays, system outages and other external dependencies separately from TrueCareCost-controlled processing time.
  • Any adjustment to a service-level clock must follow the SOW or written agreement; staff must not unilaterally change performance calculations.
  • Client changes to payer participation, provider status, fee schedules, policies, locations or system workflows must be communicated promptly.

Service-Line Operating Guidelines

9.1 Credentialing and Provider Enrollment

  • Use provider information and attestations supplied or approved by the provider / client.
  • Track application status, payer, submission date, reference number, missing documents, follow-up and effective date where confirmed.
  • Do not represent an application as approved until the payer or authorised source confirms approval and effective date.
  • Provider accuracy, disclosure, signature and final attestation remain the responsibility of the provider / client.

9.2 Eligibility and Benefits Verification

  • Record payer source, verification date, reference number where available, benefit information and limitations communicated.
  • Distinguish active eligibility from confirmation that a specific service is covered or payable.
  • Do not guarantee payment, coverage on date of service, medical necessity or final patient responsibility based solely on a verification response.
  • Escalate unclear benefits, coordination-of-benefits issues and payer inconsistencies.

9.3 Prior Authorization and Referral Support

  • Track request date, service / procedure, payer, supporting documents, reference number, status and validity period where confirmed.
  • Escalate requests requiring clinical rationale, peer-to-peer review, provider signature or treatment decision to the client.
  • Do not begin or recommend clinical treatment based on administrative authorisation status.
  • Clearly distinguish pending, approved, partially approved, denied and expired authorisations.

9.4 Medical Coding and Charge Entry

  • Code from documentation and coding rules applicable to the engagement, using current authorised references and client-approved policies.
  • Do not upcode, unbundle, infer unsupported diagnoses, alter provider documentation or code solely to achieve a reimbursement target.
  • Raise documentation queries through the approved route and retain the query outcome.
  • Modifiers, units, place of service and provider details must be supported by documentation and applicable rules.
  • Clinical interpretation and final provider documentation remain with the treating provider / client.

9.5 Claim Audit and Submission

  • Perform only edits and validation checks included in the SOW and approved workflow.
  • Record claim submission date, clearinghouse / payer acknowledgement and rejection details where available.
  • An accepted clearinghouse transmission is not confirmation that a payer has adjudicated or paid a claim.
  • Paper claim handling, special payer formats and additional attachments must be in scope or approved as a change.

9.6 Payment Posting and Reconciliation

  • Post from remittance advice, EOB, ERA or another approved source.
  • Separate payments, contractual adjustments, denials, patient responsibility and unexplained variances according to client rules.
  • Do not write off balances, alter fee schedules or make accounting adjustments without delegated authority.
  • Log unmatched payments, underpayments and reconciliation variances and route them for review.

9.7 Denial Management and Appeals Support

  • Classify denial reason using payer response and agreed categories; distinguish rejections from adjudicated denials.
  • Check the applicable response or appeal deadline and record the next action.
  • Prepare administrative corrections and supporting documentation within scope.
  • Clinical appeal arguments, medical-necessity statements, provider signatures and final appeal authorisation must be supplied or approved by the client / provider.
  • Do not guarantee reversal, payment or appeal success.

9.8 AR and Insurance Follow-Up

  • Follow the agreed payer work queue, ageing priority, call / portal protocol and follow-up intervals.
  • Record payer contact date, channel, representative / reference where available, outcome and promised action date.
  • Do not close an account merely because a call was made; close only when agreed resolution criteria are met.
  • Escalate aged, disputed, underpaid or deadline-sensitive accounts according to the client escalation matrix.

9.9 Patient Billing Support

  • Use only client-approved statements, scripts, fee schedules, payment links and communication channels.
  • Do not provide medical advice, threaten collection action, negotiate unapproved discounts or promise adjustments.
  • Patient communications must follow applicable law, client policy and TrueCareCost's contractually agreed role.
  • Refer disputes, complaints, hardship requests and sensitive patient matters to the designated client contact.

Quality, Error and Rework Policy

  • Quality review must use an agreed checklist, sample method and error definitions appropriate to the service.
  • Classify errors by severity and impact. Escalate suspected compliance, privacy or patient-safety issues immediately.
  • Correct errors through the agreed process and document correction, root cause and prevention action.
  • Where a defect originates from client source data, payer response, system configuration or client instruction, record the dependency and request correction rather than silently changing source information.
  • Repeated errors trigger focused coaching, workflow clarification or client-side corrective action as appropriate.
  • Report quality results with sample size, period, exclusions and calculation method; avoid unsupported claims based on small samples.
Severity Illustrative meaning Response
Critical Potential privacy breach, unauthorised action, material compliance concern or significant deadline / patient impact. Immediate escalation, containment and management review.
Major Material processing error with financial, operational or repeated impact. Correct, investigate root cause and assign corrective action.
Minor Isolated documentation or process deviation with limited impact. Correct and monitor for recurrence.

Communication and Client Conduct

  • Use professional, factual and respectful language in all client communications.
  • Designate approved points of contact for operational instructions, escalations and commercial matters.
  • Confirm material verbal decisions in writing, including owner and due date.
  • Do not disclose internal staffing issues, another client's information, confidential pricing or internal deliberations.
  • Do not bypass the agreed client contact structure except where an urgent incident or contractual escalation requires it.
  • Raise concerns early and provide a practical recovery proposal where possible.

Performance Measurement and Reporting

Measure performance using agreed definitions and reliable source data. The SOW or reporting plan must define the metric, denominator, reporting period, exclusions, data source, owner and target.

Metric Guideline / safeguard
Productivity / throughput Report completed units with work type and complexity context; avoid comparing unlike tasks.
Turnaround time Define start / stop points and treatment of pending client, payer and system dependencies.
Quality score Disclose sample size, error severity, sampling method and exclusions.
Rejection / denial rate Separate clearinghouse rejections from payer-adjudicated denials; define count or dollar basis.
AR ageing Use consistent ageing buckets and identify client / payer / internal pending categories.
Backlog Report opening balance, received, completed, transferred and closing balance to reconcile movement.

Set targets after a baseline period where practical. A target is a management objective, not a guarantee, unless expressly stated as a contractual service level.

Information Security and Confidentiality

  • Access client information only for authorised work and to the minimum extent required.
  • Use individual accounts, approved devices and client-approved access methods. Never share passwords, MFA codes, payer portal credentials or authentication tokens.
  • Do not copy PHI into public AI tools, personal email, unapproved spreadsheets, personal messaging applications or external storage.
  • Do not take screenshots, photographs, recordings or local downloads containing client information unless explicitly approved and secured under policy.
  • Lock screens, protect workspaces and report suspected loss, misdirection, phishing or unauthorised access immediately.
  • Follow client retention, return and secure-deletion instructions and the applicable contract.
  • Complete required privacy and security training before production access and at the required refresh interval.

Compliance note: These guidelines support a compliance programme but do not, by themselves, establish HIPAA compliance, certification or legal sufficiency. Required safeguards, BAAs, risk assessments, training records and technical controls must be separately implemented and validated.

AI, Automation and Tool Use

  • Use automation only where approved by TrueCareCost and the client, with a documented purpose, access scope, validation and fallback process.
  • Do not place PHI or confidential client data into public generative AI services or unapproved tools.
  • AI-generated coding suggestions, appeal drafts, summaries or classifications must be reviewed by a qualified authorised person before operational use.
  • Automation must not independently make clinical decisions, alter source records, submit high-impact transactions or communicate with patients unless explicitly approved and controlled.
  • Maintain an audit trail for automated actions where supported; report unexpected outputs or failures.

Attendance, Availability and Handover

  • Team members must follow the roster and coverage arrangements approved for the engagement.
  • Planned leave should be communicated under internal HR policy and early enough for queue coverage planning.
  • Unexpected absence must be reported to the reporting manager as soon as reasonably possible.
  • Before planned handover, update assigned items with current status, action history, deadline, pending dependency and next step.
  • Do not leave critical or deadline-sensitive work without a named owner or documented escalation.

Incident, Complaint and Escalation

Level Examples Required action
P1 – Critical Suspected PHI exposure, unauthorised access, major system outage, patient-safety concern or imminent material deadline failure. Immediately notify designated internal lead; follow incident response plan and preserve relevant evidence.
P2 – High Major backlog, repeated payer / system issue, widespread processing defect or material client dependency. Escalate promptly to Operations Lead / Project Lead; agree recovery owner and update frequency.
P3 – Routine Individual account issue, standard clarification or isolated correction. Log and route through normal work queue and agreed target.

Only authorised personnel may issue formal incident notifications to clients, regulators or affected individuals. Follow the contract and approved incident response plan for notification requirements.

Commercial, Billing and Payment Guidelines

  • Fees, billing units, minimum monthly commitments, implementation charges, approved pass-through costs and payment terms must be documented in the agreement / SOW.
  • Timesheets, volumes or transaction reports used for invoicing must follow the agreed measurement and approval process.
  • Client disputes must be raised through the contractual process and within the agreed review period.
  • Undisputed amounts remain payable according to the agreement, unless the contract states otherwise.
  • TrueCareCost may pause new or non-critical work for material overdue invoices only where the executed agreement permits and after required notice and escalation.
  • Fee waiver, credit, refund, penalty or service credit requires authorised management approval and written documentation.
  • Do not commence unpaid additional work based solely on an informal promise of future approval.

Business Continuity and Service Recovery

  • Maintain primary and backup contacts, queue ownership and documented handover information.
  • Where capacity or system constraints threaten delivery, inform the client promptly and provide a realistic recovery estimate.
  • Prioritise security containment, deadline-sensitive work and restoration of critical queues.
  • Temporary workarounds must be approved, time-limited, documented and consistent with security requirements.
  • Do not promise recovery timelines until the responsible technical or operational owner has assessed the issue.

Training, Competency and Policy Acknowledgement

  • Personnel must complete role-specific onboarding before independent production work.
  • Training records should include topic, date, trainer / source and completion status.
  • Competency may be assessed through supervised samples, workflow demonstrations or quality review.
  • Policy exceptions must be approved by the designated manager and documented with rationale, risk, duration and compensating controls.
  • Staff must acknowledge that they have read and understood the policies relevant to their role.

Non-Compliance and Corrective Measures

Policy violations are reviewed fairly and proportionately, considering intent, training, clarity of instruction, impact, recurrence and applicable employment / contractor terms. Possible actions include coaching, retraining, access restriction, reassignment, formal disciplinary action or contract remedies, as appropriate. Suspected misconduct, fraud, deliberate data misuse or serious security violations must be escalated to management.

No employee or contractor should be penalised for raising a genuine concern in good faith through the approved reporting route.

Exceptions and Policy Review

Exceptions require written approval from the relevant TrueCareCost authority before implementation, unless immediate action is necessary to contain a security or operational incident. Each exception must identify the policy clause, reason, affected client / process, risk, compensating control, approver and expiry / review date.

The Operations Lead owns routine review. Legal, privacy, security, HR or finance sections should be reviewed with the relevant qualified adviser or functional owner before adoption.

Governance and Client Application

This framework establishes TrueCareCost's baseline operating controls. The executed MSA, BAA, SOW and approved client-specific workflows govern the actual engagement. Any client-specific variation must be documented, reviewed and approved through the applicable change-control process.

Appendix A – Mandatory Pre-Go-Live Checklist

  • Signed agreement, SOW and applicable BAA / data-processing terms confirmed.
  • Services, exclusions, volumes, operating hours, pricing and service levels documented.
  • Client and TrueCareCost primary / backup contacts recorded.
  • Approved access, systems, devices and secure transfer methods confirmed.
  • Workflows, payer-specific instructions and escalation matrix available.
  • Staff training and competency checks completed.
  • Work queue fields, statuses, priorities and reporting definitions agreed.
  • Baseline / pilot sample and acceptance criteria agreed.
  • Change-control and invoice-dispute processes communicated.
  • Go-live approval recorded by authorised representatives.

Appendix B – Suggested Client Communication Rules

Topic Good practice Avoid
Status update State facts, current status, blocker, owner and next update. Vague statements such as “being handled” without evidence.
Delay Explain cause, impact, dependency and realistic recovery plan. Blaming the client or promising unsupported completion times.
Scope request Acknowledge, assess impact and route for written approval. Starting extra work before approval.
Payer outcome Report payer response and reference accurately. Describing eligibility or authorisation as guaranteed payment.
Quality issue Own TrueCareCost-controlled errors, correct them and document prevention. Hiding, minimising or silently changing the record.

Appendix C – Acknowledgement and Approval

I acknowledge that I have received and reviewed the TrueCareCost RCM Project Policies and Operating Guidelines and understand that I must follow the policies applicable to my role. I understand that client-specific contractual documents and approved workflows may add requirements.

Acknowledgement Details
Employee / Contractor name  
Role / Department  
Signature  
Date  
Manager / Approver  
Management approval Name / Title Signature Date
TrueCareCost authorised approver