Published: 12 March 2018
Within the XML data, the UniqueSuccessorId does represent a unique succession record in the ODS database. However, Succession in the XML supports both predecessor and successor organisations in some scenarios. The majority of records in the data have only ever been succeeded by one organisation so will only have one Succession record. By default succession actually represents predecessor relationships on the target organisation as in the example shown below:
Org X – succeeded by Org Y.
Org Y would have a succession of type “Predecessor” stored on its record.
Succession relationships are represented in this way to reflect some of the behaviour of the existing ODS products “succ.csv” and “succarc.csv”.
Where there is a longer chain of succession the behaviour is a little more complex. One thing to note though is that succession is only recorded for the immediate predecessor or successor. For
Org A – succeeded by Org B – succeeded by Org C - succeeded by Org D
Org D would have a single Succession of Type “Predecessor” to Org C only
Org C would have two Successions, of Type “Predecessor“ to Org B and Type “Successor” to Org D
Org B would have two Successions, of Type “Predecessor“ to Org A and Type “Successor” to Org C
In addition, mergers are supported via multiple Predecessor relationships on the Successor record, but there is a separate row for each of these in the data.
Note also that if the full chain of Succession needs to be derived, e.g. from PCTs back to Primary Care Groups, the Archive and the Full current file would need to be loaded into the local database.