Cerner Integration
This guide covers connecting Vigil to Oracle Health (Cerner).
Prerequisites
Before starting, you need:
- Cerner CODE Console access
- FHIR R4 endpoint URL
- OAuth2 client credentials
- System account with appropriate permissions
Work with your Cerner administrator to obtain these credentials.
Required Permissions
Your Cerner system account needs:
| Permission | Purpose |
|---|---|
| Patient read | Read patient demographics |
| Observation read | Read existing observations |
| Observation write | Write observations from Vigil |
Configuration Steps
1. Access Integration Settings
- Sign in to Vigil as IT Admin
- Navigate to Settings > Integrations
- Tap Config tab
2. Configure EMR Connection
| Field | Value |
|---|---|
| EMR Type | Cerner |
| FHIR Base URL | Your Cerner FHIR endpoint |
| Auth URL | Cerner OAuth2 token endpoint |
| Client ID | From Cerner CODE Console |
| Client Secret | From Cerner CODE Console |
| FHIR Version | R4 |
3. Configure Patient Matching
Cerner supports:
- MRN - Match on Cerner MRN
- MRN + DOB - Match on MRN and date of birth
4. Enable Data Flows
Enable desired data flows:
- ✓ Patient Census (Inbound)
- ✓ Observations (Outbound)
- ✓ Vitals (Outbound)
- ✓ Assessments (Outbound)
5. Test Connection
- Tap Save
- Return to Status tab
- Tap Test Connection
- Verify successful connection
ADT Integration
To receive patient census updates:
Cerner Configuration
Configure Cerner to send ADT messages to Vigil's webhook endpoint:
- Access Cerner integration tools
- Configure outbound ADT interface
- Point to Vigil webhook URL
- Use HL7 v2.5 format
Supported ADT Events
| Event | Action |
|---|---|
| A01 | Create patient on admit |
| A02 | Update on transfer |
| A03 | Mark discharged |
| A08 | Update demographics |
Observation Mapping
Vigil maps observations to Cerner flowsheet data:
| Vigil Data | Cerner Location |
|---|---|
| Observations | Flowsheet (custom row) |
| Vital signs | Standard vital flowsheet rows |
| Assessment scores | Flowsheet (assessment-specific rows) |
Work with your Cerner build team to configure appropriate flowsheet rows.
Troubleshooting
Authentication errors
- Verify client credentials in CODE Console
- Check system account is active
- Ensure OAuth scopes are correctly configured
Observation sync failures
- Check flowsheet row configuration
- Verify patient identifier mapping
- Review error messages in Sync Log
ADT not processing
- Verify Cerner outbound interface is active
- Check message format matches expected HL7 version
- Review ADT Log for received messages
Contact your Cerner administrator and Vigil support for complex issues.