Frequently Asked Questions | OpesCare
FAQ

Frequently Asked Questions

Everything you need to know about OpesCare.

Health ID

What is an OpesCare Health ID?

An OpesCare Health ID is a unique digital identifier that lets you carry your approved medical history with you across all partner healthcare facilities. It links your records — visits, labs, prescriptions, immunisations — into a single verified timeline.

How do I get my Health ID?

Create an OpesCare account on the registration page. Your Health ID is generated automatically and linked to your verified profile. You can view and share it from your patient portal.

Can my Health ID be used offline?

Yes. Your Health ID generates a QR code that providers can scan even without an internet connection, subject to later online verification.

Privacy & Security

Who can see my medical records?

Only providers you have explicitly authorised. Every access is recorded in your access log, visible in your patient portal. You can revoke access at any time.

How does OpesCare protect my data?

OpesCare uses AES-256 encryption at rest and TLS 1.3 in transit. All clinical data is stored in HIPAA-compliant data centres with redundant backups. We undergo regular third-party security audits.

Does OpesCare sell my data?

Absolutely not. OpesCare never sells, rents, or shares your personal or medical data with third parties for commercial purposes. Your data belongs to you.

For Healthcare Facilities

How can a hospital join OpesCare?

Contact our partnerships team via partners@opescare.com or use the contact form. Our integration team will guide you through the onboarding process, including API setup and staff training.

Which systems does OpesCare integrate with?

OpesCare integrates with major HIS/EMR systems via HL7 FHIR R4, our REST API, or the Bridge Agent for legacy systems. We also support flat-file and CSV imports for onboarding historical records.

Developers

Is there API documentation?

Yes. Full Connect API documentation is available on the Developers page, including authentication guides, endpoint references, sandbox credentials, and SDK quickstarts.

Is there a sandbox environment?

Yes. Every developer account gets access to a full sandbox environment with test data and a dedicated API key. You can test all endpoints without affecting production data.

Still have questions?

Our support team is ready to help you with any questions not answered here.

Contact Support