← Back to the category

Healthcare documentation and procedures

Visible changes after a cosmetic, dental or other procedure

Put assessment and care first. Don't wait to take photos or create a Record before seeking help. Keep the images private, including any data in their metadata and descriptions. Goal: track visible changes as a complement to care.

Create an account and start

The problem

This use applies only when there is a material consequence with a visible sign that may change before a later assessment.

Compare photos taken with similar lighting, distance and angle, without forcing positions. Keep the context and the capture conditions, so the comparison doesn't suggest clinical conclusions.

Swelling, marks, asymmetry, a prosthesis that shifts: many visible consequences change over time, improving, getting worse or being corrected by another professional. By the time the person seeks a second opinion or discusses costs and redress, the condition that prompted the complaint is already different. The photos are on the phone, mixed with everything else, in no order and with no reliable date.

This use case isn't for recording every appointment. It makes sense when there is a material consequence and something visible that may change.

What to preserve

When needed, your own photos and videos, the quote, the instructions you received, messages, expenses and related documents.

Goal: track visible changes as a complement to care.

Main file: your own photos taken in comparable conditions.

When to capture: after assessment and care have come first.

Supporting sources: medical records, the instructions you received and a professional assessment.

Limit of this scenario: on its own, the Record does not establish a diagnosis, professional error, a cause or a causal link.

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.

Photos you take yourself, from the same angle and distance and in similar light, make comparison easier. The quote, the instructions you received, messages with the clinic and receipts complete the context. Medical records and reports belong to the clinic and the professional, and copies are requested through their own channels.

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 your own photos taken in comparable conditions as your reference material and check it against medical records, the instructions you received and a professional assessment. The timestamp on a hash does not confirm a diagnosis, professional error, a cause or a causal link.

Step by step

  1. Put assessment and care first. Don't wait to take photos or create a Record before seeking help. Keep the images private, including any data in their metadata and descriptions.
  2. Compare photos taken with similar lighting, distance and angle, without forcing positions. Keep the context and the capture conditions, so the comparison doesn't suggest clinical conclusions.
  3. Preserve your own photos taken in comparable conditions exactly as it is; don't edit the file you register.
  4. Link the material to medical records, the instructions you received and a professional assessment; describe its origin and when it was captured as declared information.
  5. 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 a diagnosis, professional error, a cause or a causal link. Keep the supporting sources and read the Terms of Use.

Frequently asked questions

Does Provenia see my photos?

No. Your photos stay on your device. Only the hash and some metadata are transmitted.

How should I organize the files for this case?

Keep a private Project and register one comparable set of photos per milestone, always from the same angle and distance. Use neutral file names and descriptions that don't reveal health details, and if you share copies, strip location data from those copies only, keeping them separate from the originals.

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.

Start with three free credits

Put assessment and care first. Don't wait to take photos or create a Record before seeking help. Keep the images private, including any data in their metadata and descriptions.

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.

Create an account and start

Continue reading