Healthcare Services Addendum

Once approved and accepted, this Healthcare Services Addendum (“Addendum”) will supplement the Terms of Use between Berryhill Consulting LLC (“Rekonix”) and the healthcare customer (“Customer”). It applies to Healthcare Billing and controls over conflicting general Terms for that module.

1. Activation conditions

Healthcare Billing may accept real data only after Rekonix confirms all applicable conditions:

• An effective BAA with Customer and a verified BAA chain for every provider that may receive PHI.
• Required security, incident-response, retention, support, and minimum-necessary controls.
• Approved clearinghouse, eligibility, payment, email, statement-mail, and other live rails used by Customer.
• Applicable CPT, CDT, X12, or other licensed data and transmission rights.
• Completion of the module’s operational and accounting release gates.

2. Intended use and exclusions

Healthcare Billing supports billing operations and accounting, including patient and payer A/R, charges, claims, remittances, denials, statements, estimates, payment plans, collections status, and related reporting. It is not an EHR, clinical chart, scheduling system, clinical decision-support system, healthcare provider, health plan, or healthcare clearinghouse. Customer must not store psychotherapy notes, clinical narratives, images, treatment charts, or other clinical content outside the fields expressly approved for billing.

3. Customer compliance responsibilities

Customer is responsible for:

• Its covered-entity or business-associate status, HIPAA policies, workforce access, patient notices, authorizations, and legally required risk analysis.
• Accurate patient, provider, payer, coverage, coding, charge, medical-necessity, claim, appeal, estimate, and collection information.
• Provider enrollment, payer contracts, timely filing, claim certification, record retention, refunds, credit balances, and responding to patients and regulators.
• Reviewing every claim, payment, write-off, estimate, statement, communication, and ledger posting before relying on it.
• Configuring least-privilege users and promptly removing access that is no longer needed.

4. BAA and PHI

The executed BAA governs PHI and prevails over this Addendum. Customer will submit only the minimum PHI needed for approved billing functions. Rekonix may block a workflow or provider that is not within the approved BAA chain. Customer directs disclosures to payers, clearinghouses, patients, guarantors, payment providers, mail providers, and other recipients selected through the module.

5. Claims, eligibility, and licensed content

Scrubbing, eligibility, expected-payment, coding, and deadline tools are aids and do not guarantee coverage, medical necessity, acceptance, reimbursement, appeal success, or compliance. Customer must verify payer rules and approve submissions. Licensed code descriptors and transmission formats may be used only inside the Service for authorized healthcare billing, may not be extracted or redistributed, and may become unavailable if a required license expires.

6. Payments, statements, and collections

Customer is the provider, creditor, merchant of record, and owner of patient receivables. Rekonix does not own, buy, collect, or take assignment of debt, hold patient money, make lending decisions, or act as a collection agency. Customer directs statements, reminders, payment plans, placement exports, refunds, and collection activity and is responsible for the Fair Debt Collection Practices Act, state collection law, card and ACH rules, No Surprises Act obligations, and other laws applicable to its conduct. Patient-facing communications must identify Customer, not Rekonix, as the provider and creditor.

7. Communications and portals

Email and text, if later offered, must contain only the minimum approved information and normally direct the recipient to a protected portal. Customer is responsible for recipient addresses, communication preferences, consent, and portal access. Rekonix may expire or rotate portal links and block communications that are not within an approved provider and BAA path.

8. Data access, retention, and termination

Customer must maintain access to PHI as required by law and export records before termination. Rekonix will assist with access, amendment, accounting, return, or deletion as stated in the BAA. If return or destruction is infeasible, BAA protections continue and further use is limited to the reason making it infeasible.

9. Fees and third-party costs

The module may include a base subscription, active-provider quantities, and disclosed pass-through or usage charges for claims, eligibility, statements, licensed code sets, payments, or other vendor services. The exact amount, allowance, billing event, and renewal interval must be shown before activation or use. Incurred usage may be billed after the module is disabled.

10. Suspension

Rekonix may suspend a healthcare workflow when a BAA, license, provider contract, security control, enrollment, payment rail, or legal requirement is missing or expired. Rekonix will preserve Customer access to existing records to the extent legally and technically permitted while preventing unsafe new processing.

11. No professional or reimbursement guarantee

Rekonix does not provide medical, legal, coding, compliance, or reimbursement advice and does not guarantee payment or regulatory compliance. The disclaimers and liability terms in the Terms apply except where the BAA or law expressly provides otherwise.

12. Contact and effectiveness

Questions and requests for launch approval may be sent to support@rekonix.com. This draft becomes effective only after counsel approval, Rekonix’s written activation notice, and Customer acceptance.