# Integration Brief Worksheet

Use this before promising EHR, EMR, imaging, device, or partner-system integration. "We integrate with the EHR" is not a requirement until the path, owner, standard, and testing expectations are specific.

## Integration Summary

- Product feature:
- Customer or site:
- External system:
- System owner:
- Clinical workflow:
- Integration owner on your team:

## Interface Details

| Item | Notes |
| --- | --- |
| Standard or protocol |  |
| Message, resource, object, or endpoint |  |
| Implementation guide or profile |  |
| Direction of data flow |  |
| Authentication method |  |
| Authorization roles |  |
| Test environment available? |  |
| Expected volume |  |
| Expected latency |  |
| Downtime tolerance |  |

## Data Mapping

| Product field | External field | Required? | Transformation | Validation rule |
| --- | --- | --- | --- | --- |
|  |  |  |  |  |

## Error Handling

| Failure | Detection method | User-facing behavior | Retry or recovery | Owner |
| --- | --- | --- | --- | --- |
| Missing field |  |  |  |  |
| Authentication failure |  |  |  |  |
| External system unavailable |  |  |  |  |
| Duplicate message or record |  |  |  |  |

## Acceptance Criteria

- [ ] The exact integration standard or profile is named.
- [ ] Test data and test environment are available.
- [ ] Error handling and support path are documented.
- [ ] Security and privacy review owners are named.
- [ ] Monitoring and audit trail expectations are clear.
- [ ] The customer agrees what "done" means.