-
Notifications
You must be signed in to change notification settings - Fork 0
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
SnomedCT <-> kmehr #124
Comments
This looks like terminology work to me... The impact on the FHIR structures is low/non-existant. We need the input of a medically trained person to do this. |
To be discussed in the WG. |
This will probably have no impact on fhir structure indeed, but is very important for the implementation because we need to foresee both systems in parallel. For me it's indeed a medically trained person that should have look at this. |
Yes, hence to discuss in the wg - we cannot dismiss the possible impact before discussing e.g. mapping tables. |
This has been raised before. The WG thinks that it should be part of the eHealth platform publication |
RIZIV confirms that the mapping table will be available by end of June, including publication by eHealth platform |
In the care set for BeVaccination SNOMEDCT codes are used for the VaccineCode https://www.ehealth.fgov.be/standards/fhir/vaccination/ValueSet-be-vs-vaccine-code.html.
But we currently have to support in different exports (sumehr, PMF...) kmehr indications of the current kmehr model: https://www.ehealth.fgov.be/standards/kmehr/en/tables/vaccine-indication-codes.
Because we need to support both systems at the same time, can a mapping table be provided so we are sure to use the correct mapping between SNOMEDCT & kmehr codes.
The text was updated successfully, but these errors were encountered: