Import bundle

[SergeyGaluzo]

To avoid confusion...

Currently the only API to ingest the set of resources in real time is to POST Bundle. This API has performance and stability issues, which prompted this new work.

My goal was to extend efficient $import logic to real time calls. We should not, at least now, add any extra logic beyond $import, which might have performance impact.

$import uses ndjson as input format. Very efficient. Hence new endpoint should use this format. There is a demand, for customer convenience, support bundle format, so it was enabled too. By no means, this endpoint is a replacement of current generic bundles processing logic.

We should avoid inheriting any complexity allowed by generic bundle format. For example, $import logic (so new endpoint logic) requires resource id. We should avoid attempts to extend functionality by enabling identity search to identify resource. Maybe in future, but not now.

To avoid confusion (added because of bundle format) about what functionality is supported, I suggest refraining from using bundle in endpoint name. I suggest clarifying intent in the documentation.

This endpoint will process batch in a single database call, hence it inherently equivalent to the transaction bundle. It also either PUTs all input resources or none. This makes output response trivial (no need to have complex output logic generic bundles have).

When using bundle format, it would be nice to ignore all bundle components except Resource. We should be clear about it in the documentation. BTW I am not sure that we need to make documentation change now, we can wait till first customer provides feedback.

https://microsofthealth.visualstudio.com/Health/_workitems/edit/117904

[SergeyGaluzo]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[SergeyGaluzo]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).