Open vadi2 opened 8 years ago
Any updates on this by chance?
This is quite problematic, because standard json parser of v8 looses this information. There was long thread in FHIR chat, only solution to use string to represent such numbers.
On Tue, Oct 4, 2016, 11:50 AM Vadim Peretokin notifications@github.com wrote:
Any updates on this by chance?
— You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/fhirbase/fhirbase-plv8/issues/108#issuecomment-251330941, or mute the thread https://github.com/notifications/unsubscribe-auth/AAB9Qt3DGXzwGfdBCN07Ci-awEQePbEHks5qwhNOgaJpZM4IRaTO .
If FHIR represented them as a string, that'd be the easiest... do you have a link to the chat discussion? What was the outcome?
Using v1.3.0.13, precision for trailing 0's on FHIR decimals is lost, while it is important to keep (http://hl7.org/fhir/2016Jan/datatypes.html#precision, http://hl7.org/fhir/2016Jan/json.html#decimal)
Test case:
Resource stored in Postres according to pgAdmin:
105.0 gets turned into 105.