...
The TCS microservice can be found in the repository: https://github.com/Health-Education-England/TIS-TCS.
What it does
- Provides endpoints
...
- for the List/CRUD on People, Programmes, Posts, Placements (4xP) as core objects.
- Note that People in particular is subdivided into a primary and multiple secondary database tables and corresponding endpoints, so People has a primary Person table but 'secondary tables' of ContactDetails, PersonalDetails, GMCDetails, GDCDetails, RightToWork and Qualification - all keyed off the same Person ID, i.e. 1:1 relationship
- The relationships between the 4P Core objects are relatively complex and will be more fully documented on Entity Relationship Diagrams, the endpoints also support the creation and maintenance of these relationships
- An example would be Placements can have many Supervisors (a subset of Person records), of two types, Clinical and Educational. These have a separate PlacementSupervisor table outlined Placement Supervisors - Solution Design.
- Also provides endpoints for the List/CRUD on supporting objects, Curricula, Specialty and Rotations
- Supports the relationships between Specialties & Sub-Specialties as outlined on this page - Note: unfinished relationships are highlighted here as Jira tickets still to do
- Supports the relationships between Rotations and Programs/Posts/People, as outlined here: Programmes - Rotations - Solution Design, Field Validation & Scenarios
- Provides the endpoints to support Document Management - the storage /metadata management of externally created documents against Person records (initially).
- As other services, the TCS service also authenticates with Keycloak to obtain a JWT token and authorises its permission levels with the Profile service
Assessments
Summary
What it does
...