Healthcare documentation and procedures
A significant denial or delay by a health insurer or provider when the channel is fragile
Put your care, a reference number and a formal response first. Identify whether you are dealing with the insurer or with the healthcare provider, and use an internal review or the ombudsman where available, before treating any capture as a complement. Goal: organize the request, the response and the reference numbers.
The problem
This use only adds value when a materially significant denial or delay appears in a channel that doesn't properly keep the exact content.
Tell the insurer's response apart from the provider's communication. Ask for a reference number and a formal response; request a review or contact the ombudsman where available. A capture complements those channels.
Many responses from health insurers and providers arrive through channels that don't stay at hand: a chat that's wiped when you close it, an in-app message that disappears after an update, an authorization screen that changes status with no history, a phone call that leaves only a reference number. When you need to challenge a decision, ask for a review or show how long you waited, the exact content is no longer available.
This use case isn't for every interaction. It makes sense when the denial or delay carries real weight for your treatment and the channel used doesn't keep what was said.
What to preserve
The request or prescription where relevant, the denial or the screen, reference numbers, messages and the necessary documents.
Goal: organize the request, the response and the reference numbers.
Main file: the formal response or a complementary capture of the channel.
When to capture: after prioritizing care and asking for a reference number.
Supporting sources: the insurer, the provider, the ombudsman and any guidance from the health-insurance regulator in your country.
Limit of this scenario: on its own, the Record does not establish that coverage was owed, clinical urgency or any administrative or court outcome.
Collect only what you need, through access you are lawfully entitled to. Use neutral file names and descriptions, store files securely and share them only with people who need them. Where it is lawful to make a redacted copy, keep it as a separate file from the preserved original and note which version's hash you registered. See the Privacy Policy.
Save the full screenshot, with the date, the time and the name of whoever replied when they appear. Keep the medical request or prescription behind the request, the reference numbers and the messages exchanged. Keep the lawfully preserved file and label any redacted copies separately; the context helps people understand the response. Health data is sensitive, so register only what is necessary.
How Provenia documents this scenario
Your browser calculates the SHA-256 hash of the file you select. The file itself stays on your device: Provenia receives only the hash and metadata, meaning the file name, its size and the context fields you fill in. Provenia stores the hash and the Record data. Keep the exact file you used and the exported Dossier, because they are what make a byte-for-byte check possible later.
Three different times are involved. The time the Record was created on Provenia comes from Provenia's server and is not certified. The date of the event or capture is something you declare in the context, in the description or in the file itself, and it depends on other sources. The externally certified UTC date and time ties the hash you submitted to the timestamp authority's response; it does not certify when the event happened.
Provenia sends the hash, never the file, to FreeTSA, an external timestamp authority, which issues an RFC 3161 timestamp. Provenia validates that timestamp before the Record is completed. If FreeTSA is unavailable, or the timestamp cannot be obtained or does not validate, the Record is not created and no credit is used. Older Records created before this feature was active may have no external timestamp. A timestamp obtained today covers the hash submitted today; it is never issued later or backdated.
Each Record's timestamp is separate from the signatures on the exported Dossier: Provenia's digital signature on the PDF and the Ed25519 signature on Dossier.json. Those signatures cover the exported documents and do not certify the date of the event. See Trust and Verifiability.
In this scenario, use the formal response or a complementary capture of the channel as your reference material and check it against the insurer, the provider, the ombudsman and any guidance from the health-insurance regulator in your country. The timestamp on a hash does not confirm that coverage was owed, clinical urgency or any administrative or court outcome.
Step by step
- Put your care, a reference number and a formal response first. Identify whether you are dealing with the insurer or with the healthcare provider, and use an internal review or the ombudsman where available, before treating any capture as a complement.
- Tell the insurer's response apart from the provider's communication. Ask for a reference number and a formal response; request a review or contact the ombudsman where available. A capture complements those channels.
- Preserve the formal response or a complementary capture of the channel exactly as it is; don't edit the file you register.
- Link the material to the insurer, the provider, the ombudsman and any guidance from the health-insurance regulator in your country; describe its origin and when it was captured as declared information.
- Group the milestones in a Project and register each relevant file separately. Keep the files untouched and the exported Dossier, with a secure backup.
What the Record shows and what it does not
A Record is a private electronic document that can form part of a wider body of evidence, assessed according to its context and origin. On its own, it does not establish that coverage was owed, clinical urgency or any administrative or court outcome. Keep the supporting sources and read the Terms of Use.
Frequently asked questions
Can I use Provenia instead of the insurer's reference number?
No. The insurer's reference number comes first. A Record is an extra layer when the channel leaves a gap.
How should I organize the files for this case?
Keep the insurer's messages and the provider's messages in separate Records, each with its reference number in the description. Add the formal response when it arrives and any review or ombudsman request after it, so the order of events is clear. Register only the health information the case needs.
Which date is certified?
Only the UTC date and time in a valid external RFC 3161 response tied to that Record's hash. The time on Provenia's server and the event or capture date you declare are separate pieces of information. The timestamp does not certify when the event happened.
Official references
Technical reference for context only. It is not legal advice or a conclusion about any case. Provenia is not affiliated with, integrated with or endorsed by the organization listed.
- RFC 3161 — Time-Stamp Protocol (IETF)https://datatracker.ietf.org/doc/html/rfc3161
Start with three free credits
Put your care, a reference number and a formal response first. Identify whether you are dealing with the insurer or with the healthcare provider, and use an internal review or the ombudsman where available, before treating any capture as a complement.
Each Record covers one file. Each completed Record uses one credit, including the first one, which creates the Project. A new account includes three free Document Credits and one Project, with no payment and no card, so the starter credits cover three single-file Records. For prices and conditions, see Pricing.
Already have an account? Log in.