Privacy and preparation
What should a buyer brief for healthcare administrative data specify?
By SourceX Editorial · Reviewed by Noah Loul ·
9 sections
Short answer
A buyer brief for healthcare administrative data should name one administrative task, draw its nonclinical boundary, and list only the records and fields that task needs, each with a reason. It should also state permitted and prohibited uses, the expected de-identification method and date precision, payer and code-list context, outcome labels, and history and volume. Fields the brief cannot justify stay out of scope.
Redaction
Healthcare administrative
Key takeaways
- Require a written brief that names one administrative task and justifies every requested field before scoping any records.
- Keep coded fields payers adjudicate on, and exclude narrative notes, attachments and clinical documents by default.
- Use the standard transactions and reason codes as the administrative evidence a model learns from.
- Check day-level date needs against the de-identification method early; Safe Harbor keeps only the year.
- Label records with payer category, period and code-list version so rule changes do not blur the data.
What should a buyer brief for healthcare administrative data specify?
A useful brief names one administrative task, draws the nonclinical boundary for it, and then lists only the records and fields that task needs, with the reason each field is needed. It also states permitted and prohibited uses, the de-identification method expected, the payer and date context, the outcome labels the buyer wants, and the history and volume. Anything the brief does not justify should be treated as out of scope.
This page is written for the organization that holds the records: a medical group, a hospital revenue cycle team, a billing company or a health plan's operations group. When an AI developer asks for administrative data, the brief is what lets the organization's privacy officer, compliance lead and counsel decide whether a request can be answered at all and in what form. A vague brief, such as all claims data for the last five years, cannot be assessed and tends to pull in far more than the task requires.
Asking for a written brief is reasonable and common. It turns a conversation into a document that can be checked field by field, and it gives the buyer a clear answer instead of a slow series of objections. The template in this guide is built so that a buyer can fill it in and an organization can review it without starting from a blank page.
This guide covers administrative and operational records only. It does not address clinical decision-making, diagnosis or treatment, and nothing here is clinical advice.
Where does administrative detail end and clinical detail begin?
Administrative detail describes how care was requested, authorized, billed, paid, disputed and scheduled. Clinical detail describes the patient's condition and the reasoning behind care. The brief should keep the first and exclude the second unless a specific administrative field cannot work without it, and then name that field and the reason.
The line is not always clean. A claim carries diagnosis and procedure codes because payers adjudicate on them, so a claims dataset contains clinical information even when the task is purely financial. A prior authorization record may include an attachment with chart notes. The brief should therefore say which coded fields are needed and at what granularity, and should exclude attachments, narrative notes and documents produced for clinical purposes by default.
A practical test helps: if the model's output is an administrative action or prediction, such as whether a claim will be denied, which reason code is likely, or how long an authorization will take, the inputs should be administrative too. If a requested field would mainly help a model reason about the patient's condition, it belongs to a clinical project with a different review, not to this brief.
The scope exclusion and permitted use requirements template
The template below is the asset to send back to a buyer. Each row is a field the brief must fill, the default exclusion or limit that applies if the buyer is silent, and the evidence the organization should check before agreeing. Defaults are deliberately narrow; a buyer can argue for more by explaining why the task needs it.
Return the completed template to the buyer with every row answered, including the rows where the answer is no. A row marked excluded with a one-line reason saves a round of negotiation later, and a row marked open shows exactly which decision is still waiting on the privacy officer, counsel or an operations lead.
Keep the signed version with the dataset's documentation. When the license is drafted, the permitted and prohibited use rows should be copied into it rather than paraphrased, so that the brief and the contract cannot drift apart.
| Brief field | What the buyer must state | Default exclusion or limit | What the organization checks |
|---|---|---|---|
| Administrative task | The single workflow and model output, such as denial prediction or authorization routing | No task stated means no scoping | That the output is an administrative action, not a clinical judgment |
| Transactions and record types | Which claim, remittance, authorization, eligibility or call records, and from which systems | Only the named transaction types | That the records exist in the named systems for the full period |
| Field list with necessity | Every field requested and why the task needs it | Fields without a stated reason are dropped | A field-by-field necessity review by the privacy officer |
| Clinical boundary | Which coded clinical fields are needed and at what level | No narrative notes, attachments or clinical documents | That code granularity is the least the task can use |
| Free text | Which free-text fields, such as call notes or appeal letters, and why | Excluded unless reviewed and de-identified | Sample review for identifiers and clinical narrative |
| Identifiers and dates | The de-identification method expected and any date precision required | De-identified before delivery; no direct identifiers | Whether the date precision needed is compatible with the method |
| Payer and rule context | Payers, plan types, date range and code list versions | Records labeled with period and payer category | That rule or code changes inside the period are flagged |
| Outcome labels | Which outcomes the model learns from, such as final payment or appeal result | Only outcomes recorded in administrative systems | That outcomes are complete for the period, not truncated |
| Permitted uses | Training, evaluation or both, for which model and which deployment | Only the stated administrative task | That uses match the organization's agreements and policies |
| Prohibited uses | Uses the buyer accepts are excluded | No re-identification, linkage, clinical decision use or resale | That exclusions are written into the license, not just the brief |
Which administrative evidence does each task actually need?
Each administrative task needs a small, specific set of fields. Writing them down per task is the quickest way to apply the minimum necessary idea in practice and to show a buyer why a broad request is being narrowed.
At a glance
Which administrative evidence does each task actually need
The standard transactions help define the evidence. CMS lists the HIPAA-adopted X12 standards, including the 837 for health care claims, the 835 for electronic remittance advice and the 278 for prior authorization and referrals, all at Version 5010. Remittances explain payment differences with claim adjustment reason codes, which X12 maintains as an external code list and pairs with group codes that show who bears an amount, such as CO for contractual obligation and PR for patient responsibility. Those codes are administrative evidence a denial or payment model can learn from without any clinical narrative.
Volume and history belong in the same conversation. A buyer should state how many months of history it needs and roughly how many records per task, and the organization should check that outcomes are complete for the most recent months; claims still in appeal or awaiting payment will look like open cases, not denials or payments, if the extract stops too early.
- Denial prediction: claim header and line fields, payer category, submission and adjudication dates, adjustment group and reason codes, remark codes, final paid status. Leave out attachments and chart notes.
- Authorization routing: request type, service category, requested and decided dates, determination, stated denial reason, resubmission history. Leave out clinical justification documents.
- Appeal outcome prediction: original denial codes, appeal level, dates, outcome and adjusted payment status. Appeal letter text only after review, and only if the task depends on it.
- Eligibility and benefits checks: inquiry and response status, coverage category and timing. Leave out anything beyond what the response itself carries.
- Patient access calls: call reason category, routing, hold and resolution times, outcome. Transcripts only after de-identification review, and never for clinical content.
How do HIPAA's rules shape what a brief may ask for?
HIPAA affects the brief in three ways: how much information may be used, what de-identified means, and whether identifiable information may be disclosed for payment at all. Each answer depends on the organization's role and agreements, so the privacy officer and counsel should apply them to the specific request.
First, HHS describes the minimum necessary standard as requiring covered entities to make reasonable efforts to limit uses, disclosures and requests of protected health information to the minimum necessary to accomplish the intended purpose. A brief that justifies each field is the document that makes that judgment possible. Second, HHS guidance recognizes two de-identification methods, Safe Harbor and Expert Determination. Under Safe Harbor, listed identifiers must be removed, including all elements of dates more specific than the year that relate directly to an individual, and the organization must have no actual knowledge that what remains could identify someone.
Third, HHS states that the Privacy Rule prohibits selling protected health information without an authorization that states the organization will receive remuneration for the disclosure. That is why administrative data licensing usually proceeds on de-identified records rather than identifiable ones. Organizations that hold records as business associates face a further limit: HHS explains that a business associate may use or disclose protected health information only as its business associate contract permits or requires, or as required by law. A billing company or clearinghouse should read its agreements before answering any brief, including whether they allow it to create de-identified data for this purpose.
De-identification lowers privacy risk; it does not on its own give the organization the right to license records. Ownership of the records and any contractual limits with payers, providers or vendors still need to be checked.
Why must the brief pin payer rules, code lists and dates?
Because payer behavior and the rules governing it change, and a model trained across a change will learn a mix of two regimes unless the data says which is which. The brief should require each record to carry its period and payer category, and the organization should flag known changes inside the date range.
Prior authorization is a current example. CMS's fact sheet for the Interoperability and Prior Authorization Final Rule (CMS-0057-F) says impacted payers must send decisions within 72 hours for expedited requests and seven calendar days for standard requests, and must give a specific reason for denials. Authorization records from before and after those requirements took effect can differ in timing and in the detail of denial reasons, which matters for a model that predicts either.
Code lists change too. X12 maintains the claim adjustment reason codes as a list that is updated and from which codes are retired, so a dataset spanning several years should record which list version applied when each remittance was issued. Without that, a model can treat a retired code and its replacement as different events.
Worked example: a denial-prediction brief from a physician group
Illustrative example. An AI developer asks a multi-specialty physician group for three years of claims and remittances, payer call notes and the medical records attached to appealed claims, to train a denial-prediction model.
Run through the template, the brief narrows quickly. The task is denial prediction, an administrative output. Claims, remittances, adjustment and remark codes, payer category and dates are kept. Diagnosis and procedure codes are kept at the level payers adjudicate on, because denials depend on them. Attached medical records are excluded as clinical documents the task does not need. Call notes are deferred until a sample of about 200 notes has been reviewed for identifiers and clinical narrative.
The date requirement exposes a conflict. The developer needs day-level submission and adjudication dates to learn timing, but Safe Harbor allows only the year for dates directly related to an individual. The privacy officer sets out the options for counsel: an Expert Determination that assesses whether shifted or relative dates keep the risk very small, or a model design that uses intervals between events instead of calendar dates.
The exception comes later. After delivery planning starts, the developer asks to use the same records to evaluate a clinical documentation assistant. That use falls outside the nonclinical boundary and the permitted uses in the brief, so the answer is a separate request and review, not an extension of this one.
Which brief requests should go to the privacy officer before scoping?
Send the brief for privacy and legal review before scoping when any request below appears. These are the points where the decision depends on law, agreements or a judgment about clinical content, and where a quick yes is hardest to undo.
- The buyer asks for identifiable records, or for linkage keys that would let records be joined to other datasets.
- Requested fields include narrative notes, attachments or documents created for clinical care.
- The organization holds the records as a business associate or under payer or vendor contracts that limit secondary use.
- The task needs day-level dates or small geographic units that Safe Harbor would remove.
- Records include populations or services that carry additional protections under federal or state law.
- The permitted uses mention clinical decision support, utilization review for individual patients or resale.
Answering a brief with SourceX
If an organization answers a brief through SourceX, SourceX takes on qualification, rights review, contracting, preparation, delivery and payment for the license of its selected records. Whether a healthcare administration team qualifies is settled first in a brief assessment, and no records are uploaded for it. When a deal proceeds, nothing leaves the organization until it has approved the scope and terms and signed, and de-identification is carried out by SourceX through approved processing routes.
Frequently asked questions
What is a buyer brief for healthcare administrative data?
It is a written request in which an AI developer states the administrative task, the records and fields it needs and why, the uses it will make of them and the uses it will not. It gives the organization holding the records something its privacy officer and counsel can review field by field.
Can claims data ever be purely nonclinical?
Not entirely, because claims carry diagnosis and procedure codes that payers adjudicate on. A brief can keep those codes at the level the administrative task needs while excluding notes, attachments and other clinical documents.
Does de-identification make a healthcare dataset licensable?
It reduces privacy risk but does not settle the right to license. The organization still has to confirm it owns or controls the records and that its agreements with payers, providers or vendors allow the use.
Why would a buyer need dates more precise than the year?
Timing tasks such as authorization turnaround or denial prediction depend on intervals between events. Safe Harbor allows only the year for dates directly related to an individual, so those briefs usually need another approach, such as an Expert Determination or interval-based fields, decided with counsel.
Who should review a healthcare administrative data brief?
At minimum, the privacy officer and counsel, with someone from revenue cycle or operations who knows what each field means. A healthcare administrative expert helps judge whether the field list fits the task.
Sources
- HHS guidance states that covered entities must make reasonable efforts to limit uses, disclosures and requests of protected health information to the minimum necessary for the intended purpose. Source
- HHS de-identification guidance describes Safe Harbor and Expert Determination; under Safe Harbor all elements of dates more specific than the year that relate directly to an individual are removed and there must be no actual knowledge that remaining information could identify someone. Source
- HHS states that the Privacy Rule prohibits selling protected health information unless an authorization states that the entity will receive remuneration for the disclosure. Source
- HHS explains that a business associate may use or disclose protected health information only as permitted or required by its business associate contract or as required by law. Source
- CMS lists the HIPAA-adopted X12 Version 5010 standards, including the 837 health care claim, the 835 remittance advice and the 278 prior authorization and referral transactions. Source
- CMS's fact sheet for CMS-0057-F says impacted payers must send prior authorization decisions within 72 hours for expedited and seven calendar days for standard requests and give a specific reason for denials. Source
- X12 maintains Claim Adjustment Reason Codes as an external code list used with group codes such as CO (contractual obligation) and PR (patient responsibility), with codes added and retired over time. Source
See if your company qualifies
A short company assessment. No data uploads are needed.