Hospital Integration

Recommended architecture for integrating an HIS with Prana Connect (Wegagen Bank powered)

Reference Model

Recommended components:

HIS (billing + cashier module)

Prana Connect adapter/service (server-side)

Webhook receiver (can be the same service)

Finance/reconciliation tooling (reports + exports)

Use a stable reference scheme that never changes after creation:

HOSP-INV-YYYY-NNNNNN

Suggested fields to store per payment:

Field	Purpose
`reference`	Primary reconciliation key
`paymentId`	Prana Connect identifier
`status`	pending/succeeded/failed/expired/reversed
`amount` / `currency`	Amount correctness and reporting
`channel`	Operational support and analytics
`createdAt` / `paidAt`	Reporting and SLA tracking

Generate invoice: Generate and persist reference in your HIS before initiating payment.

Initiate payment: Create a payment intent and receive instructions (or a redirect URL).

Show clear payer instructions: Display the exact steps to complete the payment, and keep the screen non-blocking.

Confirm automatically: Update the invoice when a webhook arrives; avoid manual “refresh” as the default path.

Timeouts: Treat as unknown and poll payment status by reference until final state.

Duplicate clicks: Use idempotency keys to avoid duplicated intents.

Partial payments: Decide policy (reject, accept as credit, or split invoices) before go-live.

Keep sandbox and production separated:

Separate credentials

Separate webhook URLs

Separate monitoring/alerts