Most time, I think json is forward and backward compatible as long as some convention is kept such as adding fields only etc. I always thought so since I studied CQRS and event sourcing. Is it true for FHIR, especially firely sdk? I answered so in a discussion, however I doubted it as I didn’t do it in FHIR. Here I have a short code to demostrate the two case. In the end, the result is yes and no.

In the past several months, I called it quite intensive. I need to master the knowledge of FHIR, advanced dotnet technologies (attributes, generator, reflection, code emit, expression tree, advanced linq, customized aspnet pipeline, nuget package), code optimization technologies and several aws technologies (DynamoDB, S3, glue, spark) in depth to meet the schedule of a project. You really can’t account on solution architects or support engineers from cloud providers. I don’t get one perfect answers from them so far when I used their services.

Microsoft FHIR Server serialize searchindices this way in cosmosdb. How to model it in AWS DynamoDB? { "id": "9240cda7-bbb7-4ad4-aa9f-971750a3dc71", "searchIndices": [ { "p": "_id", "c": "9240cda7-bbb7-4ad4-aa9f-971750a3dc71" }, { "p": "_lastUpdated", "st": "2018-08-22T23:37:56.1289012+00:00", "et": "2018-08-22T23:37:56.1289012+00:00" }, { "p": "patient", "r": "Patient/example" }, { "p": "performer", "r": "Practitioner/example" }, { "p": "related", "r_0": "Observation/example-genetics-1", "s_1": "http://hl7.org/fhir/observation-relationshiptypes", "c_1": "derived-from" }, { "p": "related-target", "r": "Observation/example-genetics-1" }, { "p": "related-type", "s": "http://hl7.org/fhir/observation-relationshiptypes", "c": "derived-from" }, { "p": "status", "s": "http://hl7.

How do you extract multiple fields at different levels of nesting json resources? jsonpath, jq, jmespath or chatgpt? In FHIR, bundle resource in json format usually have multiple level of details nested in json. It’s quite different from other use cases. My first thought is using jsonpath as it is quite similar to FHIRPath. There are several limitations of jsonpath which make it infeasible. It doesn’t support to the use case, even though JsonPath supports deep scan and Bracket-notated child or children.