• API that works with SNOMED Template Language in general, then we could look at templates for specific FHIR Resources.
• Mostly a question of the actual mapping - status, severity and negation will cause problems.

Group requested an example use case - input and output expectations. DK: CIMI have looked at this previously (see attachments), resource needs to be constrained in a detailed way to allow such a mapping to be safely performed ie restrict resource only to those things that can be expressed in the SNOMED concept model.

ML thought the API would be fairly dumb and populate template (passed in) slots from values appearing in a resource ie no interpretation of semantics.

Bindings (using some path specific to the implementation model) were suggested in the languages group, distinct from the slot names. Use case query - would it instead be possible to work directly with the information model.