Services

Hi all,

Following yesterday’s call, and Mark’s suggestion that we should be thinking about what “services” the interoperability layer needs to provide.

I think the capabilities the interoperability layer needs fall into three categories: ones that are invisible to edge applications, ones that are served by a single registry, and ones that require coordination between registries.

Transparent services

  • Authorise
  • Encrypt
  • Route
  • Normalise

Cross-registry capabilities

  • Care plan
  • Register encounter

Single-registry capabilities

  • Lookup provider
  • Lookup facility
  • Lookup health record
  • Lookup terminology terminology
    I’d be particularly interested in any more that people can suggest that fall into the cross-registry category, as I think that’s where most of the complexity (and therefore discussion) will fall.

Cheers,

Chris