Skip to content

Rights and contracts

Healthcare data vendor responsibility map: who handles each deal step

By SourceX Editorial · Reviewed by Noah Loul ·

10 sections

Short answer

Assign every step of a healthcare administrative data deal to one accountable party, and tie that step to the document that permits it. The provider or health plan decides scope and field necessity; a billing vendor acts only as its business associate agreement allows; de-identification happens before anything leaves; and the license names who holds the dataset afterward. Any step without a named owner and a written permission stops the deal.

Redaction

Healthcare data vendor

This page covers healthcare data vendor responsibility map: who handles each deal step.Illustrative

Key takeaways

  • Every step needs one accountable party and one written permission; a step with neither stops the deal.
  • The provider or health plan keeps scope, field necessity and the licensing decision even when a vendor holds the records.
  • A business associate may de-identify only if its agreement allows it, and may not use client PHI for its own purposes.
  • Keep clinical narrative outside administrative datasets and justify every code that edges toward clinical content.
  • Mark each permission as confirmed, assumed or unknown, and extract nothing on an assumed row.

How should a healthcare administrative data deal assign responsibilities at each step?

Give each step exactly one accountable party and one written permission. In a deal built on billing, scheduling or prior authorization records, the covered entity (the provider or health plan) owns the decision to use the records, any vendor that holds them acts only within its business associate agreement, and the dataset that leaves is de-identified before it reaches a licensee. When a step has two owners, or an owner without a document behind it, that is where deals fail review.

A healthcare data vendor responsibility map makes this visible. It lists the steps from scoping to deletion, names who performs and who approves each one, and records the clause, policy or report that authorizes it. The map does not replace counsel. It gives counsel and the privacy officer one page on which to find the gap before records move.

Keep four questions separate while filling it in. Who can technically reach the records (access) is not who may use them (privacy permission), and neither settles who owns them or what a contract allows them to license. De-identification removes the records from the HIPAA Privacy Rule, but it does not create a right to license data a contract restricts.

Which parties sit in an administrative data deal, and what are their HIPAA roles?

Start by classifying every party, because the role decides what it may do. HHS describes covered entities as health plans, health care clearinghouses, and health care providers that conduct standard transactions such as claims and eligibility inquiries electronically, including when a billing service sends them on the provider's behalf.

A business associate handles protected health information (PHI) on behalf of a covered entity, and HHS says a subcontractor that creates, receives, maintains or transmits PHI for a business associate is itself a business associate that needs its own written agreement before PHI changes hands. A cloud host that stores the billing vendor's data is usually one of these.

The AI developer that licenses the finished dataset is usually none of these. It receives de-identified records under a license, so its obligations come from that license and from any non-HIPAA law that still applies, not from a business associate agreement.

Which parties sit in an administrative data deal, and what are their HIPAA roles?
PartyTypical exampleUsual HIPAA roleWhat limits its part in the deal
Provider organizationMulti-site physician groupCovered entityPrivacy Rule permissions, its own policies, payer and vendor contracts
Health planRegional insurer's claims operationCovered entityPrivacy Rule permissions, plan sponsor and provider agreements
Billing or revenue cycle vendorOutsourced coding and denial management firmBusiness associateOnly the uses its business associate agreement permits
Vendor's subcontractorHosting provider or offshore work queue teamBusiness associate (subcontractor)Its agreement with the vendor, which must meet the same standard
De-identification performerInternal privacy team or outside expertDepends on who performs it and on whose behalfMust be authorized to use the PHI for that purpose
Dataset licenseeAI developer building an operations agentUsually outside HIPAA once data is de-identifiedThe license terms and other applicable law

Who may de-identify the records, and under which document?

The covered entity, or a business associate whose agreement expressly allows it. HHS treats de-identification as a use of PHI, so a business associate may de-identify records it holds for a covered entity only to the extent its business associate agreement authorizes it. HHS's sample contract language suggests the parties state whether the business associate may de-identify and what it may do with the result.

HHS recognizes two methods: Safe Harbor, which removes specified identifiers with no actual knowledge that the remainder could identify someone, and Expert Determination, in which a qualified person applies accepted methods and documents that the risk of identification is very small. Information that meets either standard is no longer PHI.

This matters for licensing because HHS says a covered entity may not sell PHI to a business associate or any other third party for that party's own purposes without authorization. A limited data set under a data use agreement is also not a shortcut: HHS describes it as usable for research, public health and health care operations, which counsel has to match against the actual AI use before relying on it.

The counsel reviewed role and obligation mapping worksheet

Use the worksheet below as the working document for the deal. Each row is one step; a row is complete only when the accountable party has signed off and the evidence column points to a real document. Counsel reviews the permission column before any extraction begins, which is why the worksheet carries that name.

The counsel reviewed role and obligation mapping worksheet
StepAccountable partyPermission or documentEvidence the step is doneStop if
1. Define the administrative taskCovered entity operations leadInternal approval naming the task and its nonclinical boundarySigned scope page listing included workflowsThe task needs clinical judgment to label outcomes
2. Inventory source permissionsCovered entity privacy officer with counselBusiness associate agreements, payer contracts, vendor termsContract register with relevant clauses quotedAny contract forbids secondary use or is missing
3. Decide field necessityCovered entity privacy officerMinimum necessary policy applied to the field listField dictionary with a reason for each fieldA field has no stated purpose
4. Extract from the source systemWhoever holds the system under the agreementThe agreement clause covering this useExtraction log with system, query and date rangeThe holder's agreement does not cover the use
5. De-identifyCovered entity or authorized business associateSafe Harbor procedure or expert determinationMethod record or signed expert reportFree text or rare values defeat the method
6. Review the nonclinical boundaryAdministrative domain reviewerScope page from step 1Sample review notes with excluded fieldsClinical narrative survives in the sample
7. Sign the licenseCovered entity as licensorDataset license agreementExecuted agreement with permitted usesRights in step 2 remain unresolved
8. DeliverLicensor or its delivery agentDelivery terms in the licenseTransfer record and checksumDelivery path exposes records not yet de-identified
9. Handle incidentsEach party for its own systemsBreach notification terms in each agreementIncident log and notification recordNotice duties are unassigned
10. Close outEach holder of extractsReturn or destruction termsWritten destruction or retention confirmationCopies remain with no stated reason

Which billing and authorization fields belong in the extract, and which clinical detail stays out?

Keep the fields that describe the administrative work and its outcome, and justify every field that edges toward clinical content. HHS's minimum necessary guidance asks covered entities to take reasonable steps to limit uses and disclosures of PHI to the minimum needed for the purpose, and to set policies for routine disclosures and individual review for non-routine ones. A field list with a reason for each field is how that review becomes checkable.

At a glance

Which billing and authorization fields belong in the extract, and which clinical detail stays out

For a denial management or prior authorization task, the necessary evidence is usually the work itself: the payer, the status history, reason codes the payer returned, the actions staff took, the dates of each step (shifted or generalized if the de-identification method requires it) and the final administrative outcome. Diagnosis and procedure codes may be needed to explain why a payer acted; each one belongs on the worksheet with its purpose stated.

Free-text clinical narrative, attached medical records, images and physician notes stay outside an administrative task. They add identification risk, they invite the dataset to be used for clinical inference it was never scoped for, and they rarely improve an operations model enough to justify the review they require.

  • Usually necessary: payer, claim or request status sequence, payer reason codes, staff actions and queue movements, step timestamps, final outcome.
  • Justify field by field: diagnosis and procedure codes, place of service, provider specialty, authorization criteria references.
  • Leave out: clinical notes, attached records, images, free-text appeal letters that quote the chart, and anything that lets a reader infer a specific patient's condition beyond the task.

What changes when a billing vendor holds the records?

The vendor can perform steps, but it cannot authorize them. HHS states that a covered entity may not hand PHI to a business associate for the business associate's own purposes, so a revenue cycle vendor that holds a client's claim histories cannot license them on its own initiative, even after de-identifying them, unless its agreement with that client allows both the de-identification and the use.

In practice this splits the map. The covered entity stays accountable for steps 1, 2, 3 and 7. The vendor may carry out steps 4 and 5 if the agreement is amended or already permits it, and it must flow the same limits to any subcontractor that touches the extract. If the agreement is silent, the usual routes are an amendment the covered entity signs, or extraction back to the covered entity so its own team de-identifies the records.

Vendors serving many providers face one more rule: records from different clients are governed by different agreements. A vendor-side dataset combining several clients needs every client's permission, recorded per client, before the records are pooled.

Which unconfirmed assumption would redraw the map?

The assumption most likely to flip the outcome is the role classification in step 2. If a party assumed to be a business associate turns out to be acting for its own purposes, or a vendor's agreement does not reach de-identification, every later row changes owner or stops. Mark that assumption as confirmed only when counsel has read the clause.

Show uncertainty in the worksheet itself rather than in a cover email. Add a status to each permission cell: confirmed (clause quoted and reviewed), assumed (believed true, not yet read), or unknown. A deal can scope and plan with assumed cells; it cannot extract, de-identify or sign with them.

Other assumptions worth marking explicitly: that state health privacy laws add nothing for the records in scope, that payer contracts carry no confidentiality clause covering remittance data, that the de-identification method survives free-text fields, and that no record belongs to a client of the vendor who never agreed.

Worked scenario (illustrative): denial histories held by an outsourced billing firm

This scenario is illustrative, not a real deal. A physician group with 3 sites wants to license 24 months of denial and appeal work queue history to developers of revenue cycle agents. The records sit in a billing firm's work queue system, hosted by a cloud provider, and the group's own practice management system holds the claims.

Mapping the steps exposes three decisions. First, the billing firm's business associate agreement covers billing services but says nothing about de-identification, so step 5 cannot run on the firm's side until the group signs an amendment, or the firm returns an extract to the group's privacy team. Second, the group's contract with one payer carries a confidentiality clause on remittance details, which moves that payer's fields to assumed until counsel reads it. Third, a sample of 200 appeal records shows that free-text appeal letters quote chart notes, so the boundary review in step 6 removes the letter text and keeps only the appeal outcome and dates.

After those changes the map has a single owner per row: the group's operations lead for scope, its privacy officer for fields and permissions, the billing firm for extraction under the amended agreement, an outside expert for the expert determination, and the group as licensor. The point where further review was needed was visible in the worksheet, not discovered after delivery.

Who handles incidents and close-out once the records have moved?

Each holder handles its own systems, and the agreements say who tells whom. Under HHS's Breach Notification Rule, a business associate that discovers a breach of unsecured PHI must notify the covered entity without unreasonable delay and no later than 60 days after discovery, and the parties can agree on shorter timelines. The worksheet's step 9 should name the contact and timeline for each hop: subcontractor to vendor, vendor to covered entity.

At termination, HHS's sample business associate contract provisions call for the business associate to return or destroy PHI where feasible, and to extend protections to anything it must keep. Interim extracts made for the deal fall under the same rule, so step 10 asks every holder for written confirmation.

The de-identified dataset is a different object. Once it meets a de-identification standard it is no longer PHI, and retention, deletion and onward use are governed by the license. Writing those terms into the license, rather than assuming HIPAA covers them, closes the last gap in the map.

Where SourceX fits in a healthcare administrative deal

Administrative records from billing, scheduling and authorization work can become licensed AI datasets through SourceX, which handles rights review, contracting, preparation and delivery. With health records, the worksheet above comes first: which party may de-identify, under which agreement, and which fields stay out.

A provider or plan begins with a brief company assessment that requires no records. It approves scope and terms and signs before any data reaches SourceX, and the signed agreement states what may be done with the de-identified dataset afterward. Under SourceX's standing terms de-identification is done by SourceX through approved processing routes, so for health records the provider's counsel confirms which agreement covers that arrangement before anything moves.

Frequently asked questions

What goes in a role and obligation worksheet for a healthcare data deal?

One row per step from scoping to close-out, with the accountable party, the document that permits the step, the evidence it was done and a stop condition. Add a status to each permission cell (confirmed, assumed or unknown) so counsel can see which rows still depend on a clause nobody has read.

Can a medical billing company license de-identified client data on its own?

Not without its client's permission. HHS treats de-identification as a use of PHI that a business associate may perform only if its agreement allows it, and a covered entity may not give PHI to a business associate for the business associate's own purposes. The client covered entity has to authorize both the de-identification and the licensing use.

Does a business associate agreement cover licensing a dataset to an AI developer?

Usually not. A business associate agreement governs how a vendor handles PHI on the covered entity's behalf; the AI developer that receives a de-identified dataset is typically bound by a separate license agreement. Both documents belong in the worksheet, and counsel checks that they do not contradict each other.

Is a limited data set enough for an AI training deal?

Often not. HHS describes limited data sets as usable for research, public health and health care operations under a data use agreement, and the agreement restricts what the recipient may do. Whether a given AI use fits one of those purposes is a question for counsel; most commercial licensing deals rely on de-identified data instead.

Who is responsible if a breach happens during extraction?

The party whose system or custody the breach occurred in, under its agreement. HHS requires a business associate to notify the covered entity without unreasonable delay and within 60 days of discovering a breach of unsecured PHI, and contracts may set shorter timelines. The worksheet should name each notification hop in advance.

Sources

  • HHS describes covered entities as health plans, health care clearinghouses and providers that conduct standard transactions electronically, including through a billing service acting for them. Source
  • HHS states that a subcontractor handling PHI for a business associate is itself a business associate, and that a covered entity may not give PHI to a business associate for the business associate's own purposes. Source
  • HHS explains that de-identifying PHI is a use of PHI, so a business associate may de-identify only to the extent its business associate agreement authorizes it. Source
  • HHS sample business associate contract provisions set out permitted uses, return or destruction at termination, and suggest stating whether the business associate may de-identify. Source
  • HHS guidance describes the Safe Harbor and Expert Determination methods and explains that de-identified information is not PHI. Source
  • HHS marketing guidance states that a covered entity may not sell PHI to a business associate or any other third party for that party's own purposes. Source
  • HHS describes limited data sets as usable for research, public health and health care operations when the recipient signs a data use agreement. Source
  • HHS minimum necessary guidance asks covered entities to make reasonable efforts to limit PHI uses and disclosures to the minimum necessary for the purpose. Source
  • HHS's Breach Notification Rule requires a business associate to notify the covered entity of a breach without unreasonable delay and no later than 60 days after discovery. Source

See if your company qualifies

A short company assessment. No data uploads are needed.

See if your company qualifies