rips/cloud
ESOpen RipsCloud →
Integrate the full process · Available with subscription

Your software. The same RIPS flow.

Integrate RipsCloud use cases from your server. The production contract includes workspace permissions, revisions, validation and evidenced submission. API access is part of the subscription.

AudienceHIS, ERP, software houses and integration teams
InputHTTP requests with a PAT and JSON data
OutcomeAn integration based on the production contract
Product scope

Tools for your process.

See product functions and process requirements.

01

Production OpenAPI

See operations, schemas, required fields and examples in the developer portal.

02

Personal tokens

Create a PAT with workspaces, permissions and expiry from the portal. The secret is shown once.

03

Full RIPS flow

Save, correct, validate and request submission of the current revision.

04

Controlled retries

Use idempotency keys for external actions and reconcile uncertain results.

05

Health documents

Issue health invoices and notes through RipsCloud and prepare the related RIPS.

06

Traceable responses

Read stable error codes, request identifiers, statuses and evidence.

Work journey

Every step keeps its context.

Prepare data, review the result and keep evidence.

01

Create your PAT

Sign in with your phone and select token permissions and workspaces.

02

Read context

Read the workspace and provider configuration before preparing data.

03

Integrate the use cases

Implement save, revision, validation and submission according to the contract.

04

Manage the result

See statuses and attempts. Resolve an uncertain result before resending.

Limits

What this product does not promise.

  • The API uses the current user and workspace permissions.
  • HTTP 200 alone is not Ministry acceptance.
  • Idempotency does not skip business validations.
  • The API does not offer direct access to the SISPRO token.

Integrate with the production contract.

Read the documentation or talk with the team about your organization setup.