OpenCRVS' data model is therefore an extension to FHIR .... #9926
-
|
.... and we have yet to find any Civil Registration process that cannot be interpreted using FHIR. (this is an extract from the documentation)< https://documentation.opencrvs.org/technology/standards/fhir-documents >, but was wondering if someone could confirm this position still stands, as well as get more details on it. Essentially, if I understand this correctly, instead of designing and building opencrvs' own data-structures, the team decided to adopt FHIR's data structures and concepts. I think this is genius because it saves us from the mapping exercise into the FHIR ecosystem. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
Hi @bzmrgonz thanks for the message. Our position up until v1.8 has definitely been to use FHIR as a data model because of the reasons stated above. However we have noticed over the years that using FHIR in the database layer has proved too expensive to maintain. OpenCRVS v1.9 will represent a major refactor allowing any vital event to be registered without the need to define FHIR standards for each event. Between the upcoming releases of OpenCRVS v1.9 & v1.10, we have decided to move FHIR from the database layer to the interoperability layer. To upgrade, any country that is using OpenCRVS v1.8 has to write a database migration unique for their form configuration. We are supporting all the countries we work with through the process. If you need help with this, please reach out. |
Beta Was this translation helpful? Give feedback.
Hi @bzmrgonz thanks for the message. Our position up until v1.8 has definitely been to use FHIR as a data model because of the reasons stated above. However we have noticed over the years that using FHIR in the database layer has proved too expensive to maintain. OpenCRVS v1.9 will represent a major refactor allowing any vital event to be registered without the need to define FHIR standards for each event.
Between the upcoming releases of OpenCRVS v1.9 & v1.10, we have decided to move FHIR from the database layer to the interoperability layer. To upgrade, any country that is using OpenCRVS v1.8 has to write a database migration unique for their form configuration.
We are supporting all th…