Make patient data shareable when patient created in OG

[andreievg]

This is only when patient is created in OG and vaccinations need to be shared across sites, does't impact immediate deployments

Is your feature request related to a problem? Please describe 👀

In this and parent PRs: #7264, we've added ability to share patient data cross site (for vaccinations). This will not work when patient is created in OG (as it won't be present in omSupply Central

Describe the solution you'd like 🎁

Sync patient to omSupply Central, when name store join is created: https://vscode.dev/github/msupply-foundation/open-msupply/blob/7160.3-Vaccine-card-integration-tests/server/service/src/apis/api_on_central/mod.rs#L68-L72

Describe alternatives you've considered 💭

Additional context 💌

Moneyworks Jobcode 🧰

[lache-melvin]

Flagging high high severity - will currently break patient fetch of all OG and existing patients to OMS remote sites!

Also, vax card sync won't work for any existing patient, not just OG ones. Though could be resolved by added changelog for all patients and their name_store_joins

[lache-melvin]

We think most cases will be covered by:

• Add changelogs for name/name_store_join for existing patients on migration, to push to OMS central
• Add back the name link id for vaccination records changelog migration
• Ensure vaccination pull deps include name/name_store_join!
• On COMS name_store_join endpoint - call OG to add name_store_join for that patient for OMS central (so patient gets synced to COMS in future) - hold connection to remote site until manual sync of COMS to OG is complete
  • This might require some testing in terms of reasonable time frames...

Part of requirements for this issue is to document handled and not handled use cases, and what happens in the patient fetch flow. Need to discuss OG patients, patients created on OMS, migrated patients, re-initialised patients...

[andreievg]

Add changelogs for name/name_store_join for existing patients on migration, to push to OMS central

❤

Add back the name link id for vaccination records changelog migration

Not necessary, actually might break things on central. vaccination records will be updated to have the name_link_id set when it's upserted on central (at which point name and name store join will be available.

Ensure vaccination pull deps include name/name_store_join!

🥇

On COMS name_store_join endpoint - call OG to add name_store_join for that patient for OMS central (so patient gets synced to COMS in future) - hold connection to remote site until manual sync of COMS to OG is complete
This might require some testing in terms of reasonable time frames...

🎉

Part of requirements for this issue is to document handled and not handled use cases, and what happens in the patient fetch flow. Need to discuss OG patients, patients created on OMS, migrated patients, re-initialised patients...

🤓

Bonus -> it doesn't hurt to re-send vaccinations to omSupply central from remote, on migration