Skip to main content

Patient Record Links and Bookmarks: Return to the Right Chart Securely

A patient-record bookmark should help an authorised user return to the intended record, while the application rechecks current access and shows clear patient context. The address is a navigation reference, not a credential, a permanent copy of the record or permission to share it. Test login expiry, branch changes, record merges and revoked access before relying on bookmarked links.

By Bractis · Updated · 8 min read

Indian clinic staff who revisit patient records, send internal task references or ask a software supplier how record links behave.

Decide whether the link identifies a patient, visit or document

A longitudinal patient record, a particular consultation and an issued document serve different purposes. A bookmark intended for the patient's history should not unexpectedly resume an unrelated unfinished visit. A document link should not be mistaken for permission to edit the underlying record.

Ask the supplier to explain the destination in ordinary clinic terms. Which object does the link identify? Does it open the current record or a specific historical item? What happens if that item is amended, merged or no longer available? A neat-looking address does not answer these questions.

Keep navigation separate from action. Merely opening a bookmark should not sign a note, create another booking, issue a document or alter a patient balance. Those operations need their own authorised workflow and understandable outcome.

Use an internal task reference when the purpose is to ask a colleague to review something. Include only the necessary context through an approved channel, and let the recipient access the record using their own account. Copying the sender's session or secret link defeats that separation.

Do not build a clinic process around a guessed URL structure. Application routes can change, and a route that happens to open today may not be a supported sharing or deep-link feature. Confirm the intended behaviour and a stable way to find the same item through ordinary navigation.

Require current authority even when the reference is known

An obscure record identifier is useful for reference, but it is not an access decision. Someone who obtains or guesses a link still needs the appropriate current authority to view the record. This is the distinction between identifying an object and authorising an operation on it.

OWASP's authorisation guidance calls for checks on each request and protection against access through manipulated identifiers. In a clinic evaluation, use controlled synthetic accounts with different permissions to inspect the expected allowed and denied paths.

Check facility scope explicitly. The same doctor may work at two locations, while a receptionist may be assigned to only one. A bookmark created in one context must not silently make that record available in another merely because both branches use the same software.

After login expiry, the application can offer an appropriate return to the intended destination, but it should establish the user's identity and access first. If the newly signed-in person has different permissions, the original user's ability to open the link is irrelevant.

Do not test by probing real patient identifiers or sharing live clinical links with unauthorised people. Arrange a synthetic evaluation with the supplier. The desired evidence is correct enforcement, not an improvised attempt to access somebody else's record.

Source: OWASP: Authorization Cheat Sheet

Do not turn browser history into a patient summary

A link containing a name, phone number, diagnosis or other private detail can expose that information outside the clinical record. Browser history, copied messages, logs and support screenshots may retain the address. Avoid adding patient details to a URL merely to make it easier for staff to recognise.

OWASP documents information exposure through query strings and explains that HTTPS alone does not remove it. Encryption protects transport; it does not make every place that stores or displays the address private. Exact exposure depends on the surrounding implementation.

An opaque reference also deserves appropriate handling because it can still be linked to a person inside the application. Removing a name from the address does not make a private chart suitable for public analytics, public sitemaps or unrestricted messages.

Review the bookmark's label as well as its address. A shared reception computer may display bookmarks on screen or synchronise them through a browser profile. A patient name in the bookmark bar can reveal information even if the underlying page requires login.

If an inappropriate link has already been shared, use the clinic's incident and access process. Changing the current address cannot guarantee deletion of earlier copies, logs or screenshots. The response should match what was exposed and who may have received it.

Source: OWASP: Information exposure through query strings in URL

A denied bookmark can be a correct result

In the fictional eight-link set, six destinations may resolve after authentication and merge checks, one should deny access and one should explain that the item is unavailable. Counting every opened page as success would reward the wrong behaviour for the restricted record.

Review a patient-record link

Use these prompts in your clinic’s own notes. Record the result, responsible person and next action for each item.

Identify the object
State whether the link represents a patient, visit, task or document version.
Check authority
Use agreed synthetic roles to verify current access and facility scope.
Inspect exposure
Review private URL parameters, bookmark labels and where links are copied.
Test change
Include expired login, a merged record, an amendment and revoked access.

Questions doctors ask

Sources and scope

Updated on . Original link-lifecycle model. No private routes were probed, access controls tested against real records or guarantees made about permanent links, browser-cache removal or product security. No independent clinical or legal review is claimed.

Try the workflow
with Bractis.

Ask Bractis to demonstrate supported record links with synthetic data across current access, expired login, a role restriction and a changed record. Confirm patient identity and document version after each return.

Request a clinic demo