Where does your PHI go with an AI coding vendor?

Jessica Miller, MHA, CPC, CPC-I

10 min read · November 17, 2026

Photograph of a security reviewer standing in a server aisle following a run of network cabling along a rack, representing a PHI data-flow review of an AI medical coding vendor

Where does your PHI go with an AI coding vendor?

Ask an AI medical coding vendor five things: how PHI reaches them, where it is processed, who can see it, how long it stays, and what leaves. Certifications come after those answers. MediCodio AI publishes its controls and names the questions that still belong on a call. The checklist below works on any vendor.

The form arrives with a date on it. The business wants this one cleared by Friday, and the vendor's site shows three certification badges and nothing about where the charts go.

Why does AI coding change the PHI question?

The data flow is longer than the one your team is used to reviewing.

Charts leave the EHR through an integration or an automation, reach the vendor, get processed by a model, pass through a review step, and return as codes attached to a claim.

Each hop is a question. Where does the chart sit while it waits? Which systems touch it? Who at the vendor can open it? What does the vendor keep after the claim goes out? The same questions run through data privacy in AI-driven coding systems .

The HIPAA Security Rule sets national standards for protecting electronic PHI held by a covered entity or its business associate, and requires administrative, physical and technical safeguards. How a specific vendor built its pipeline is the part you have to ask about.

For an RCM company the stake is sharper. The PHI belongs to your clients, and HHS counts a subcontractor that handles PHI on behalf of a business associate as a business associate too. A subcontractor decision you get wrong becomes your client's breach notification.

What should you ask about PHI handling?

Copy this into your vendor call. The questions work for any AI coding vendor, including the ones you are comparing. Group them by the path the data takes.

How PHI arrives tests whether the vendor can describe the connection in specifics. Where it is processed should name environments and any third party in the path. Who can see it is a least-privilege question. How long it stays is where vague answers cost the most: a vendor holding charts after the claim is paid has become a custodian of your clients' data. What leaves covers model training. Ask that one in writing.

Ask the vendorWhat a good answer contains
How does a chart get from our EHR to you?A named mechanism (API, RPA process, certified EHR integration), the authentication method, and who holds the credentials.
Is every hop authenticated and encrypted in transit?Confirmation for each leg, including the return of finished codes.
Where is PHI processed and stored?Named environments and hosting arrangements, and whether processing happens in more than one.
Which sub-processors touch PHI?A current list, what each one does, and notice when it changes.
Who at your organization can open a chart containing PHI?Roles rather than names, the basis for granting access, and how often it is reviewed.
How is access removed when someone leaves?An offboarding process tied to the identity system, with a timeframe.
How long do you retain PHI after the claim is submitted?A stated retention period, what triggers deletion, and whether backups follow it.
What happens to our data when the contract ends?A documented return or destruction process, and evidence you can hand your client.
Do you use our charts to train models?A yes or no, the contractual basis, and whether no is the default.
Can you produce a log of who accessed a given chart?A demonstration during the call.
Will you sign our BAA, and do those terms flow to sub-processors?A yes to both, with the mechanism for the second.
Who do we call at 2am during a suspected breach?A named role, a contact path, and a notification commitment in the contract.

What should you ask about certifications?

Reviewers read certifications as a pass or fail stamp. They are evidence, and each one carries a scope.

SOC 2 Type 1 against Type 2. A Type 1 report describes controls at a point in time. A Type 2 report examines whether those controls operated over a period. The AICPA publishes the SOC suite of services and the trust services criteria behind it, covering security, availability, processing integrity, confidentiality and privacy. Ask which criteria the report covers, because a SOC 2 scoped to security alone says nothing about confidentiality. Then read the exceptions and the complementary user entity controls, the list of things the report assumes you are doing.

ISO/IEC 27001:2022. The current edition sets requirements for an information security management system. It certifies that security is governed, operated and improved as a system, rather than certifying any particular control. The certificate carries a statement of applicability and a defined scope. Ask for both. One scoped to a corporate office tells you little about the platform processing your charts.

HIPAA. There is no HIPAA certification, so a compliance statement is a self-assessment. Ask what the vendor's most recent risk analysis found and what it changed.

What should you ask about incidents and access?

Most reviewers spend their energy on prevention and stop before the part that decides a bad day.

Ask who at the vendor declares an incident, what their threshold is, and who sits on the escalation path. Ask how the vendor notifies you, how fast, and whether that sits in the contract or in a policy the vendor can revise. Under the HIPAA Breach Notification Rule, a business associate must notify the covered entity without unreasonable delay and no later than 60 days from discovery, so the contractual timeline needs to leave your own obligation room to run.

Then ask what makes an investigation possible.

  • Can the vendor show you, during the call, a log of actions taken on a single chart?
  • How long are those logs retained, and can your team pull them without a support ticket?
  • Does the vendor run third-party assessments and penetration testing, and will it share a summary?
  • How does access get provisioned, reviewed and removed, and who signs off?
  • What security training do the people handling your clients' PHI receive?

How does MediCodio AI answer this checklist?

The certifications and controls below are reproduced from the MediCodio AI security and compliance page .

SOC 2 Type 2, attested by a CPA firm, 2026. Our controls for security, availability, and confidentiality were examined in operation over time and attested by an independent CPA firm under the AICPA SOC for Service Organizations program. The SOC 2 Type 2 report is available under NDA.

ISO/IEC 27001:2022. Our information security management system is certified against the current international standard, covering how security is governed, operated, and improved.

HIPAA. Protected health information is processed, maintained, and stored in accordance with HIPAA, with encrypted PHI exchange and access limited to the roles that need it.

Veradigm Connect, certified October 2025. Certified for direct EHR integration, so charts move between your system and ours through a vetted, supported connection rather than an ad hoc export.

On controls:

  • Encryption of PHI. Protected health information is encrypted in exchange between your systems and ours.
  • Role-based access control. Access to systems and data is granted by role, kept to the minimum the role needs, and reviewed.
  • Comprehensive audit logging. Actions on charts and codes are logged, so who did what, and when, is a record rather than a memory.
  • Independent security assessments. Third-party security assessments and penetration testing probe the platform from the outside, on a recurring basis.
  • Incident response. Documented protocols define how incidents are reported and handled, with named roles responsible for the response.
  • Workforce security training. Team members are trained on security protocols and HIPAA compliance, so the people handling PHI know what handling it safely requires.

RCM reviewers checking client data separation across tenants will find that covered under AI medical coding for RCM companies .

What are the red flags in a vendor security review?

Four answers should slow a review.

  • The vendor will not state a certification's scope. A badge without a statement of applicability or a defined report boundary is a logo.
  • The vendor cannot produce a log during the call. Audit logging that lives only in a policy document is a plan.
  • The vendor answers a data-flow question with a marketing claim. Accuracy rates answer a different question. You asked where the chart goes.
  • The vendor treats model training as a detail. If the answer is not in writing, assume it is unsettled.

The published controls sit on the security and compliance page , the workflow under AI medical coding , and the engagement model for RCM companies . Outside security, there are 10 more questions to ask an autonomous coding vendor .

Bring your security questionnaire to a call .

Frequently asked questions

Is HIPAA compliance enough when evaluating an AI coding vendor?

No. There is no HIPAA certification, so a compliance statement is a self-assessment and a floor rather than a differentiator. Ask what the vendor's most recent risk analysis found, how PHI is handled at each hop, and what independent examination its controls have been through.

What is the difference between SOC 2 Type 1 and Type 2?

A Type 1 report describes controls at a point in time. A Type 2 report examines whether those controls operated over a period. For a vendor processing PHI, ask for Type 2, then ask which trust services criteria it covers and read the exceptions and the complementary user entity controls.

Do we need a business associate agreement with an AI coding vendor?

A vendor that creates, receives, maintains or transmits PHI on behalf of a covered entity or another business associate falls within HHS's definition of a business associate, and HHS publishes sample contract provisions. Confirm the agreement, and confirm its terms flow down to any sub-processor that touches PHI.

What should happen to our PHI during a security incident?

Ask who declares an incident, what the escalation path is, which roles own the response, and how fast you are notified. A business associate has no later than 60 days from discovery to notify the covered entity, so the vendor’s commitment has to leave room for your own. Get the timeline into the contract.

Sources

See it in action

Ready to transform your medical coding?

See how MediCodio's AI platform delivers 98%+ accuracy across deployments since 2023, with turnaround under 24 hours at enterprise volume, inclusive of coder review, across 35+ specialties.

About the Author

JM
Jessica MillerMHA, CPC, CPC-I

Founding Member & Product Evangelist

Jessica Miller is the Head of Coding Operations at MediCodio, where she leads our AI-powered medical coding services with over a decade of experience in medical coding, compliance, and healthcare management. She specializes in developing innovative medical coding workflows that combine human expertise with cutting-edge technology to deliver exceptional accuracy and efficiency for healthcare organizations.

LinkedIn

Loading posts...

Frequently Asked Questions

Is HIPAA compliance enough when evaluating an AI coding vendor?
No. There is no HIPAA certification, so a compliance statement is a self-assessment and a floor rather than a differentiator. Ask what the vendor's most recent risk analysis found, how PHI is handled at each hop, and what independent examination its controls have been through.
What is the difference between SOC 2 Type 1 and Type 2?
A Type 1 report describes controls at a point in time. A Type 2 report examines whether those controls operated over a period. For a vendor processing PHI, ask for Type 2, then ask which trust services criteria it covers and read the exceptions and the complementary user entity controls.
Do we need a business associate agreement with an AI coding vendor?
A vendor that creates, receives, maintains or transmits PHI on behalf of a covered entity or another business associate falls within HHS's definition of a business associate, and HHS publishes sample contract provisions. Confirm the agreement, and confirm its terms flow down to any sub-processor that touches PHI.
What should happen to our PHI during a security incident?
Ask who declares an incident, what the escalation path is, which roles own the response, and how fast you are notified. A business associate has no later than 60 days from discovery to notify the covered entity, so the vendor’s commitment has to leave room for your own. Get the timeline into the contract.
Who at an AI coding vendor can see our charts?
Ask for roles rather than names, the basis for granting access, how often it is reviewed, and how it is removed when someone leaves. Then ask the vendor to show you an access log for a single chart during the call. A vendor that cannot produce one on request will struggle during an investigation.