General Architecture
...
ConnectionRequestLog | Notes |
|---|---|
id | |
gmcId | |
gmcClientId | |
newDesignatedBodyCode | |
previousDesignatedBodyCode | |
reason | |
requestType | |
responseCode |
Exception Logs
Note: This does not go to GMC and exists purely in our system
ExceptionLog | Notes |
|---|---|
gmcId | |
errorMessage | |
timestamp |
Hidden Connection Logs
Note: This does not go to GMC and exists purely in our system
HiddenConnectionLog | Notes |
|---|---|
gmcId | |
reason | |
requestType | |
requestTime |
DoctorsForDB
The service tis-revalidation-connection currently breaks microservice architecture by accessing the doctorsfordb repository directly (currently should be held and maintained by tis-revalidation-recommendations)
It appears to only have one repository method which is currently unused
Elasticsearch
See existing documentation for implementation details:
Elasticsearch
The intention is to maintain an Elasticsearch index for each “tab” in the connections application, i.e:
Current Connections (implemented)
Historic Connections (implemented)
Discrepancies (implemented)
Hidden (not implemented)
These indexes consist of subsets of the following fields: Elastic Search Index Fields
The specifics of these subsets are currently under discussion