Stream: hapi
Topic: Lengthy concept property values
Lin Zhang (Nov 13 2020 at 12:57):
How to deal with lengthy concept property values? For some CodeSystems we want to import, there are some concept property values (String type) that have more than 500 characters.
Grahame Grieve (Nov 13 2020 at 13:03):
is that a problem?
Grahame Grieve (Nov 13 2020 at 13:04):
some of your very long loinc names...
Grahame Grieve (Nov 13 2020 at 13:04):
what is it that you chinese people have in those?
Lin Zhang (Nov 13 2020 at 13:53):
@Grahame Grieve Not so many. They are often comments/notes/instructions. Say, how to use a medication/charge item code. It's hard to say they are problems.
Lin Zhang (Nov 13 2020 at 13:56):
As a workaround, such a string value would be temporarily split into two or more substrings (as two instances of the same property).
Lin Zhang (Nov 13 2020 at 13:59):
The Chinese translations of LOINC terms have no such an issue.
Grahame Grieve (Nov 13 2020 at 19:45):
ok, but why split them up?
Lin Zhang (Nov 14 2020 at 06:41):
The field has a length constraint of 500 characters for the value.
Grahame Grieve (Nov 15 2020 at 10:37):
which field where?
Lin Zhang (Nov 15 2020 at 11:27):
HAPI FHIR JPA Server's DB table trm_concept_property, and its field prop_val.
Grahame Grieve (Nov 15 2020 at 21:29):
ah ok
Last updated: Apr 12 2022 at 19:14 UTC
