Stream: fhir/infrastructure-wg
Topic: Async FMM for FHIR R5
Josh Mandel (Jan 18 2022 at 20:12):
Given the language at
The asynchronous request pattern, based on rfc 7240 , caters to this use case and is applicable for all the Defined Interactions and for Operations, although for many of these uses it brings no benefit. Servers may choose which interactions the pattern should be supported on (if at all), and servers may choose to only support some of the operations using the asynchronous pattern.
We're trying to figure out the right FMM level for this part of the spec in FHIR R5. Now, with respect to use in Bulk Data operations, it makes sense to call this FMM4. But we don't have experience working with this async pattern for arbitrary FHIR interactions, and I think we probably will want more/different techniques in that context ... because if we're going to call it FMM4, we should try to apply that maturity level to custom operations like $export where we actually have experience with it, and not for interactions like FHIR CRUD (see discussion).
Josh Mandel (Jan 18 2022 at 20:12):
FYI @Dan Gottlieb
Last updated: Apr 12 2022 at 19:14 UTC
