INTERFACE ID |
IB63 – Store (Inbound to RMS) |
|||||||||||||||||
SOURCE |
External |
|||||||||||||||||
DESTINATIONS |
RMS |
|||||||||||||||||
INTEGRATION STYLE |
Asynchronous – Unidirectional |
|||||||||||||||||
DESCRIPTION |
RMS will expose an API that will allow external systems to create, edit, and delete stores within RMS. |
|||||||||||||||||
DATA |
|
|||||||||||||||||
DEPLOYMENT |
RIB |
|||||||||||||||||
INTEGRATION SERVICE LEVELS |
Guaranteed, once-only delivery to destination |
Yes |
||||||||||||||||
Scheduled data exchange |
No |
|||||||||||||||||
Audit-trail kept for data exchange (state historical duration of audit trail) |
Auditing at message level. |
|||||||||||||||||
Alerting required should data exchange fail? |
Yes |
|||||||||||||||||
Retry of data exchange necessary? (state number of times before error is logged or failure condition is met) |
Yes. RIB Hospital. |
|||||||||||||||||
Data purge on data transmittal? |
Yes |
|||||||||||||||||
Security on data exchange required? |
No |
|||||||||||||||||
PERFORMANCE SERVICE LEVELS |
If this is a server application, what is the design-time number of concurrent clients that will be serviced? |
|
||||||||||||||||
Priority of integration (High, Medium, Low)? |
|
|||||||||||||||||
Fail-over required? |
|
|||||||||||||||||
Expected response time or batch processing window |
N/A |
|||||||||||||||||
Frequency of messaging or batch data exchange |
|