Investigate ways to speed up FHIRJsonParser
See original GitHub issueFHIRJsonParser is currently generated from FHIR structure definitions using com.ibm.fhir.tools.CodeGenerator. The current structure of the parser is to check for all possible elements which results in more map lookups and method invocations than are needed for a typical instance. A better structure might be something like this:
Patient.Builder builder = Patient.builder();
for (String key : jsonObject.keySet()) {
switch (key) {
case "active":
builder.active(parseBoolean(...));
break;
case "gender":
builder.gender(parseString(...));
break;
// ...
}
return builder.build();
Issue Analytics
- State:
- Created 2 years ago
- Comments:10 (4 by maintainers)
Top Results From Across the Web
performance testing · Issue #134 · hapifhir/hapi-fhir
We should investigate using ASM or Javassist or something to speed this up. Another possibility would be to use code-genned helper methods ......
Read more >Parsing and Serializing - HAPI FHIR Documentation
A built in parser can be used to convert HAPI FHIR Java objects into a serialized form, and to parse serialized data into...
Read more >Advanced FHIR search features | Cloud Healthcare API
This page explains how to search for FHIR resources using more advanced query functionality available through the projects.locations.datasets.
Read more >An Interactive Visualization Tool for HL7 FHIR Specification ...
The FHIR resource schema in JSON contains two types of key elements “$ref” and “properties.” Our method supports the automatic parsing of the...
Read more >FHIR Data | FHIR Support in InterSystems Products
If a FHIR payload is in JSON, for example in an Interoperability request or response, you can convert it to a dynamic object...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

I have created the following issue: https://github.com/IBM/FHIR/issues/2432
Personally I think
Deferral of resource deserializationis on the same order of magnitude as #2417 (and I actually like it a bit more). Should we open an issue for that idea?