You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For this issue, I reference to #21
For code, the business rules say:
'La codification LOINC est proposée dans FHIR ; un code LOINC fait référence à la méthode d’analyse, son paramètre qui sont précisés, sauf s’il n’existe aucune ambiguïté sur l’un de ces aspects. Celle-ci a été utilisée dans les observations relatives aux assuétudes et complications à la naissance. La norme SNOMED est celle qui a été utilisée dans le cadre des observations eBirth, conjointement avec la norme LOINC pour les composants'
Discussed in WG on 13 June. The business rules document has to clarify this more @annenerenhausen
Be aware that there is an overlap between Loinc & Snomed CT. Snomed codes will have to be limited.
WG will take it up once business rules have been clarified
For this issue, I reference to #21
For code, the business rules say:
https://build.fhir.org/ig/hl7-be/core-clinical/branches/issue-21/StructureDefinition-be-observationcodeableconcept.html --> here i see that at the moment all snomed and loinc codes are acceptable? Will this be limited? Or not? Because we are mapping our EPD codes to SNOMED and we want to make sure that we are mapping on SNOMED codes that will be present in the final ValueSet.
Are there opinions on certain restrictions on this valueSet or can we go wild and map to all SNOMED codes?
The text was updated successfully, but these errors were encountered: