[Integration] BSrE — E-Signatures

Certified e-signatures.

BSrE integration built into the system's core — signing sessions directly from the EMR, status tracking, verification, and an audit trail. The certificate is a separate subscription from the provider; we are honest about that boundary.

Why now

E-signatures are shifting from nice-to-have to the core of the claims flow.

Certified e-signatures have long been treated as an optional extra. The JKN electronic-claims direction (the 30 July 2026 joint circular) changes that: claim-supporting clinical documents are steered toward being signed electronically — not scanned — as part of an auditable data chain.

Because certificate issuance involves identity verification for each clinician, this is not preparation that can be crammed overnight. Hospitals that start early stay in control of their own deadline.

E-signature flow

From certificate to signed document.

[01]

Certificate issuance & KYC

The e-signature certificate is issued by the provider (BSrE, under BSSN) after identity verification of the clinician. The certificate subscription belongs to the hospital/individual — it is not part of the Adievia license.

[02]

Signing sessions from the EMR

Clinical documents — medical resumes, physician letters, consents — are submitted to a signing session directly from the EMR flow, with no manual export-import round trips.

[03]

Certified signature

Documents are signed using the provider-issued certificate; each document's status is tracked, with a callback from the provider when the process completes.

[04]

Verification & audit trail

Signed documents can be verified, and the full cycle — submission, signing, outcome — is recorded on the system audit trail.

Honest status

The integration module is ready; the certificate is not ours to sell.

Adievia does not issue e-signature certificates and does not sell an "already e-signed" status. Certificates are issued by the provider (BSrE) as a separate hospital-owned subscription, and production activation follows the provider-side process. The technical specifics of e-signatures in JKN electronic claims also await the circular's implementing guidance — we adapt as soon as the rules are published.

Full guide to JKN electronic claims

FAQ

Questions about e-signatures & BSrE.

A scanned signature is just an image — it proves nothing about who signed and is trivially copied. A certified e-signature is issued by a state-recognized electronic certification provider (BSrE, under BSSN) and bound to the signer's identity through a verification (KYC) process, giving it legal standing under the applicable regulations.

The 30 July 2026 joint circular steers JKN claims onto SATUSEHAT-integrated EMR — and, as reported, e-signature adoption is part of the transition period. Claim-supporting clinical documents are steered toward being signed electronically, not scanned. With full enforcement targeted for 2027, hospitals that start the certificate process early will not be stuck in an issuance queue at the deadline.

No — and we state that plainly. Certificates are only issued by electronic certification providers such as BSrE. What Adievia provides is the integration: signing sessions directly from the EMR, status tracking with provider callbacks, document verification, and an audit trail. The certificate subscription is separate and belongs to the hospital.

Three things: an agreement/subscription with the certification provider (BSrE), the identity-verification (KYC) process for the clinicians who will sign, and a decision on which documents require certified signatures in your clinical flow. Then the module is activated — we guide the path from certificate application to the first signed document.

Next step

Get e-signatures in place before they become a claims prerequisite?