Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

What are possible options to convert an entire ecosystem from R4 to R5? #2

Open
bdc-ehealth opened this issue Nov 10, 2023 · 4 comments

Comments

@bdc-ehealth
Copy link
Collaborator

Just brainstorming, regardless of feasibility...

  • Parallel systems, with one system extinguishing by gradual conversion (by practitioner?)
  • Big bang Conversion of resources
  • Mixed system, one system supporting both R4 and R5
  • Parallel systems, with a gateway that translates R4 to R5 (new resources only R5)
  • Hybrid system part of the functionality in R4, part of the functionality in R5
@bdc-ehealth
Copy link
Collaborator Author

bdc-ehealth commented Nov 10, 2023

Dimensions of the above options:

  • conversion manual/automatic
  • storage one/dual
  • API one/dual
  • functionality all-in-one/some-has-different version
  • transition gradual/big-bang
  • conversion yes/no

@bdc-ehealth
Copy link
Collaborator Author

Some elements of a hybrid system are described in this document: https://docs.google.com/document/d/1UUxCpMmkyr3z4_Au7x3SslKfwcb1ILLr/edit

@bdc-ehealth
Copy link
Collaborator Author

This is a test to simply compile core with fhirVersion 5.0.0 : hl7-be/core#64 and https://build.fhir.org/ig/hl7-be/core/branches/issue-64/

@bdc-ehealth
Copy link
Collaborator Author

bdc-ehealth commented Feb 23, 2024

For some strange reason, the google doc above is not editable anymore. I replaced the document by this one: https://docs.google.com/document/d/1v8U3GK-AWbVpFQg2XZ4uHPn5vWbAdJ_cyk1vE-SSiqM/edit because of new information.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant