Notice: This guidance is under active development by NHS England and content may be added or updated on a regular basis.
Use Case - Match Parents on General Register Office (GRO) Civil Birth Registration
| User Story Summary (Clinical Overview) |
As the Related Person Network,
I want to create child-parent RelatedPersons from GRO Civil Birth Registrations,
So that more child-parent RelatedPersons are available to API consumers.
|
| Actors (Role) |
ONS, DPS, RPN |
| Frequency of Use |
Weekly (Batch for historic load). |
| Triggers |
- Weekly Birth Registration Batch sent via MESH from ONS.
- Historic Birth Registration data stored in DPS.
|
| Pre-conditions |
- Civil Birth Registration has the following fields:
- Parent surnames (Mother and Second Parent).
- Parent DOBs (Mother and Second Parent).
- Parent gender (Mother and Second Parent).
- Parent forenames (Mother and Second Parent).
- Mother postcode.
- Mother’s maiden name.
- Child’s NHS number.
- Child’s postcodes.
|
| Post-conditions |
- A successfully matched RelatedPerson is available on the API.
- Provenance indicates the source of the data.
|
| Main Flow |
- GRO Civil Birth Registration data is sent to the Related Person Network in a batch.
- For each Birth Registration:
- A search against the mother data is completed.
- A search against the second parent data is completed.
- Matched parents are persisted as RelatedPersons in the Related Person Network.
- Provenance resource is created for the relationship in the Related Person Network
- Provenance indicates the source of the data.
|
| Alternate Flow |
- When a unique match is not found for a parent, then the parent is not added as a RelatedPerson on the child’s record.
|
| Exception |
- Given that a child’s record has a mother or father RelatedPerson with an NHS number:
- When a parent match is found with a different NHS number:
- The parent matched by RPN is not added to the child’s record as a RelatedPerson.
- An NBO work item is raised.
|