...
Additional information for a provider record
name needs rematching to check if it still matches the current consensus name
- if the name matches a different record, the provider record is re-attached. If any other provider records were relying on this provider name to provide relationships, then the other provider names/consensus names need to be reattached to the appropriate node according to those prrovider records
Accidental reuse of provider record ID for a different name
this is an issue, so should be detected on import and reported back to the provider
Removal of information
Removal of record (no deprecation)
this is an issue, so should be detected on import and reported back to the provider
At integration 2 scenarios - the consensus record is supported by another provider record AND this is the only provider record for the consensus name
- we need to be testing consensus against consensus names to detect names with no provider records and names that should match now but are still separated
Deprecation of record
Updates to Concept Records
Additional information provided