Everything your reviewers ask, before they ask.

Yes. Where the engagement requires one, the applicable Business Associate Agreement is executed before protected health information is exchanged. That sequence is not negotiable and it is not an afterthought: the free review is deliberately structured so the business-level conversation happens first, with no patient information involved at all.

Soft Appeals can work from your organization's BAA. If your legal team requires its own form, that is the normal case and it is usually faster.

The minimum necessary for the denied claims assigned to Soft Appeals. In practice that is claim-level information for the specific denials in scope: the denial notice and reason, claim and payer information, the amounts, dates of service, and the supporting documentation a particular denial requires.

What is not required: unrestricted access to your EHR, your full patient database, administrator credentials, shared staff logins, unrelated clinical records, or every denial in your organization. The initial review starts with an agreed set of 20 claims and expands only where there is a reason.

Scope is agreed at claim level before information moves, so what arrives is what the assigned claims need rather than whatever an export happened to include. Patient identifiers are kept out of working materials that do not require them, and where a document can do its job without an identifier, it does.

No. No public form on this site accepts a file upload, and none asks for patient-level information. The two forms that take free text run a check that blocks a submission carrying a pattern that looks like patient information, and tells the person what it caught.

Patient-level information is requested only after the privacy documentation and an agreed secure intake process are in place, and that instruction comes as its own explicit step.

Return or disposition of protected health information at termination, and the treatment of any permitted retained copies, are governed by the executed Business Associate Agreement and service agreement rather than by a statement on a web page. Access to any client system provided to Soft Appeals is removed when the work concludes.

Business records of the engagement itself, such as invoices and correspondence about scope, are a separate category from PHI and are treated as such.

Privacy, security and vendor-review correspondence goes to support@frimpomaasync.com, which reaches Nana Frimpongmaa directly. Use it for questionnaires, contractual questions, or anything your review process requires in writing.

Do not send patient information to that address. It is a business contact, not an approved channel for protected health information. The secure channel for claim information is established separately, after the agreements are in place.

Retention periods are being set alongside the executed agreements and the applicable requirements, rather than published as a number that later turns out to conflict with a client's own contractual obligations. Where your organization requires specific retention or disposition terms, raise them before the agreement is signed and they can be addressed in it directly.

Soft Appeals is founder-operated. Access to client claim information is limited to the people performing the recovery work for that client, which today means a small, named set rather than a department. If that ever changes, the answer to this question changes with it and this page changes on the same day.

Access is scoped to the purpose it was granted for, requested rather than assumed, and removed when the work concludes.

Individual credentials, never shared logins. Where a system supports multi-factor authentication, it is enabled. Where a system cannot support it, client information does not go in that system.

That is a statement about how accounts are configured. It is deliberately not a claim about encryption standards, key management or any other technical control belonging to a service provider, because those are that provider's controls to attest to, not Soft Appeals'.

Through an agreed channel established before anything is sent, so your team knows where information is going before it goes. Ordinary email and open chat tools are not the channel for patient information, and Soft Appeals will not ask you to use them for it.

If your organization prefers its own secure system, portal or transfer method, that is usually the better answer, and Soft Appeals will work inside it.

An incident-response process is documented and can be provided to your reviewers. The specific notification obligations, including timing, are set in the executed Business Associate Agreement, decided with counsel, for your engagement.

No notification timeframe is published on this page on purpose. A number posted on a marketing page is a commitment a vendor can be measured against before anyone has confirmed it is the right one, and your organization may require something stricter than a generic figure.

Available to a reviewer with a legitimate need as part of the due-diligence process. Request it below and say who is asking, so the response is written for the right audience.

Coverage is being arranged. Until a policy is in force, no coverage or limit is stated here, and no certificate is offered. If your procurement process requires specific coverage or limits as a condition of engagement, raise it before the agreement is signed. Discovering a hard insurance requirement after a BAA is executed wastes everyone's month.

Yes, and Soft Appeals says so plainly rather than burying it. Technology assists with administrative preparation: organizing claim information, drafting documents from the applicable payer requirements, and keeping records consistent. That is where its role ends.

It does not decide whether a claim is appealed. It does not make clinical, coding, coverage or legal determinations. It does not submit anything to a payer. Every recommendation is reviewed by a person, and every submission is prepared for client approval before it goes anywhere.

The Recovery Lab demonstrates the same principle publicly: recommendations are explained through factors a reviewer can check, and no probability score appears anywhere in the method.

No. Client information is not provided for training public or general-purpose models, and services whose terms would permit that use are not used for client information.

Only approved services, under the appropriate agreements, may touch client claim information. Open consumer chat tools are not among them, and patient information is not pasted into one. Where a tool has not been through that assessment, it does not get used for client work.

Not in public material, which is a general practice across everything frimpomaasync.com publishes rather than an evasion specific to this. Vendors are named to a reviewer conducting due diligence, alongside what function each performs, whether PHI is involved, and what agreements are in place.

Service providers supporting the work are assessed against the same six questions before anything client-related touches them: what function it performs, whether PHI is involved, where information is processed, what contractual protections apply, whether it uses subcontractors of its own, and what happens to information when the relationship ends.

The list of services that touch client claim information, and what is in place with each, is provided to a reviewer conducting due diligence rather than published. Request it below.

Processing locations for the services involved are covered in the vendor disclosure provided during due diligence. Where your organization has a data-residency requirement, raise it before the agreement is signed so it can be addressed rather than discovered.

No. Client approval before submission is a standing control, not a courtesy extended to careful clients. Prepared materials are presented in final form for approval, and your team can approve, request changes, or decline.

The payer pays your organization directly. Soft Appeals does not receive, hold or route your reimbursement at any point.

Exactly one party, and it is recorded. Every claim in an engagement carries a status, an owner and a next action, so the question of where something sits has one answer rather than a conversation. The Recovery Lab shows this working on fictional claims.

No. Your billing operation keeps the revenue cycle. Soft Appeals works the denied claims assigned to it, and where a claim needs something only your team can provide, that request is recorded against the claim with a named person rather than left in an inbox.

If a billing company currently owns your denial workflow, the appropriate representative can be brought into the process. Clear roles prevent two people working the same appeal.

Termination rights and notice are set in the service agreement, and information handling at termination follows the executed agreements. Work in progress at termination, and what happens to claims already submitted, are addressed there rather than left to be worked out at the time.

The assessment you receive is yours regardless of whether you continue, including after a free review that leads to nothing. Treatment of in-flight recovery work is set in the agreement.