
Reimbursement claims that reach the fund complete at the first submission
Health funds and insurers each have their own tariffs and their own required documents, and when a claim comes back the front desk has to contact the patient again. We deal only with this administrative side.
Between admissions and administration, where the reimbursement stalls
At admissions the operator checks whether the patient has active cover, whether the service falls under the agreement and whether prior authorisation is needed, working from an agreement text that often circulates in several versions. After the service, administration gathers the referral, the medical report and the invoice and sends the claim, which the fund sometimes rejects because of a missing document or a code that is not provided for. The time is lost in these repeated checks and in the claims sent back, which mean calling the patient again.
The agent checks requirements and documents, the operator sends
In the example the agreements go into the Company Brain, each with the version in force, the tariffs and the documents required. At the time of booking the agent compares the service with the patient's agreement and tells the operator if authorisation is needed; after the service it checks that the file is complete and prepares the claim for the fund. The operator checks it and sends it, and it is for the operator to tell the patient that a service is not covered, because the news concerns the patient directly.
- The service is booked under the patient's agreement
- The agent checks requirements and authorisations against the agreement in force
- After the service it checks the documents and prepares the claim
- The operator checks, sends to the fund and speaks to the patient
Illustrative example
What agreements and reimbursements need
| Item | In this case |
|---|---|
| Data | In this caseAgreements with their versions, tariff lists, services booked and delivered, administrative documents, the outcomes of claims already sent |
| Modules | In this caseCompany Brain, Agents, Governance, Security |
| Who decides | In this caseThe operator on sending the claim and on what is communicated to the patient; administrative management on the agent's rules and, with whoever is accountable for data protection, on the documents the agent reads |
| What we measure | In this caseClaims rejected or sent back by the fund, the time between service and submission and calls to the patient for missing documents, against the starting point |
| AI Act risk class | In this caseThe case is administrative: it plays no part in clinical decisions and neither assesses risk nor sets premiums for health insurance, a high-risk use under Annex III. Because many uses of AI in healthcare are high-risk, we set the class and the boundaries with risk, compliance and data protection before development. The GDPR treats health data as a special category |
| Where to start | In this caseWith Mapping, to understand which agreements generate the most rejected claims and to decide with the relevant functions which data is needed, by whom and for how long |
With agreements that have no definite version it is worth waiting
If nobody can say which version of an agreement is in force, or if the changes agreed with the fund sit in an email exchange, the agent would apply out-of-date rules and the claims would come back all the same. The texts have to be collected and dated first, with whoever manages relations with the funds. If instead the errors arise upstream, in the coding of services, it is better to start there.
The case is part of the healthcare page.
Let's look together at the claims the fund has sent back
Starting from the reimbursement claims rejected in recent months, we look with administration at why they came back and which data was already there.