Pre-Attendance

Pre-Attendance is OSIGU's API for the check-in stage of the revenue cycle — everything that happens before the patient is seen. Where the RCM billing API documents a clinical encounter after care so it can be invoiced, Pre-Attendance anticipates the documental and eligibility validation before care, so the reception desk can catch missing documents and coverage problems while the patient is still there.

The goal is to reduce glosas (payer rejections) and revenue at risk that today only surface after care, when they are expensive to fix.

Same platform, same credentials

Pre-Attendance is part of the OSIGU RCM platform. It uses the same OAuth2 client credentials as the RCM billing API — see Obtaining tokens. What differs is the base URL and the endpoints.

What you can do with Pre-Attendance

Receive appointments from your HIS

Push scheduled appointments into OSIGU as they are created in your Hospital Information System. The endpoint is idempotent: re-sending the same appointment merges new charges without duplicating it.

Register appointments manually

A reception user can create a pre-appointment by hand as a fallback when the HIS integration isn't available for a given flow.

Collect the required support documents

Upload the documents each procedure needs. AI/DVS validation runs the same rules as the RCM account-assembly flow — but nothing is ever hard-blocked.

Configure required documents per procedure

Load, per provider product code, which support documents are mandatory — via an asynchronous CSV upload.

Core ideas

A pre-appointment is a check-in record, not a billing account

A pre-appointment represents one scheduled/checked-in visit: the beneficiary, the payer, the doctor, the appointment date, and the charges (procedures/products) expected for it. It exists before care and before any invoice. It is created either from HIS inbound (automatic) or manually (the reception fallback).

The system never hard-blocks care

This is the central business rule. Missing mandatory documents or a not-eligible beneficiary produce warnings and recorded pendencias (visible to the billing team downstream) — never a block. The reception user can always confirm the appointment and let the patient through, with no justification or approval step.

Documents are placeholders that get completed

When required supports are configured for a charge, the pre-appointment starts with PENDING document placeholders. Uploading a file completes the matching placeholder. Documents that arrive from the HIS are automatically marked RECEIVED and cannot be deleted; only manually uploaded ones can be removed or cleared back to PENDING.

Almost everything reads from the provider's catalogs and the RCM platform

Providers, payers, doctors, and product codes are resolved from the platform (via the authenticated token and the RCM API), not stored here. You reference them by their codes.

Support-config upload is asynchronous

Loading which documents are required per product code is a CSV upload that returns 202 Accepted with a process_id. A worker parses and validates it in the background; you poll the process to see the result and download a per-row validation-errors CSV if any rows failed.

Who this is for

• Hospitals and clinics running a reception / admissions desk that wants documental and coverage validation before care.
• HIS / PMS integrators that push scheduled appointments and their procedures into OSIGU as they happen — this is the first inbound endpoint of the ecosystem (push HIS → OSIGU).

Environments

Pre-Attendance is reached under its own path on the platform host. Build against sandbox first.

Sandbox

API base: https://sandbox.osigu.com/pre-attendance-api

OAuth token: https://sandbox.osigu.com/v1/oauth/token

Integration testing. Use while building.

Production

API base: https://api.osigu.com/pre-attendance-api

OAuth token: https://api.osigu.com/v1/oauth/token

Live traffic. Switch after sandbox is green.

Endpoint paths in this section are listed without the base — /v1/checkin/appointments means https://sandbox.osigu.com/pre-attendance-api/v1/checkin/appointments in sandbox.

Getting started

1. 1Reuse your OSIGU credentials

   Pre-Attendance uses the same client_id / client_secret as the RCM billing API. If you're already integrated, you're ready. If not, see Obtaining tokens.

2. 2Push (or create) a pre-appointment

   Integrate the HIS inbound endpoint, or create one manually.

3. 3Upload the required documents

   Complete the pending document placeholders — see Upload a document.

4. 4Confirm the check-in

   Move the pre-appointment to CONFIRMED. Remember: missing supports never block this step.

Support

For onboarding or production incidents: support@osigu.com.