...
Specialities effectively act as a categorisation system within TIS. They are applied to Posts, Placements and Curricula (currently). There is some complexity in how this categorisation is applied to Posts and Placements, so this will be explored in more detail below, in summary:
As of there are 138 Specialities with a status of Current (1048 in total if you include Inactive ones)
...
Note: there is an ongoing discussion / request with data quality leads to limit the Placement Primary Specialty and Other Specialty dropdown contents to those of the parent Post Jira Legacy server System JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status serverId 4c843cd5-e5a9-329d-ae88-66091fcfe3c7 key TISDEV-4258
(How does this business rule overlap with the constraint of SpecialtyType=Placement?
Suggestions that its useful for certain types of Placements which don't have a Post or other edge cases - do you want to codify these into the system, or leave the edge cases at TIS Admin discretion?)
These relationships are all stored in a TCS table called PlacementSpecialty as seen below using a PlacementSpecialtyType field:
...
| View file | ||||
|---|---|---|---|---|
|
<<check with Former user (Deleted) we can remove content after this>>
Downstream Impacts
Record Management
- records can be created using any Specialty, smart search enables users to select any specialty without limitation
- This goes against user understanding, so may require monitoring
Reporting
- not including specialty type does not impact report
- specialties are not reported on i their own right, so as long as specialties can be assigned to Post, Placement, Curricula then no further impacts
Summary
...