Library

Browse and search developer information

Portal

Pattern Description

Portal

Allows clinicians to view information in a consistent user interface even though that information has been extracted from a variety of systems. This can allow clinicians to see information from across specialities and care settings without the information having to actually move between the various clinical systems used.

Integration between the portal and clinical systems is managed on a case-by-case basis and typically does not rely on standardisation although it can benefit from it (e.g. Get Document List, Get Document). In some cases integration engines may be used manage the connectivity.

Benefits

  • Portals typically try to present the information in a consistent fashion, and provide a single known point to find information regardless of which local system it is held in.
  • Once information is exposed via a portal, this can potentially be extended to allow viewing from other services, or even by the patient.

 Concerns

  • Information extracted from the individual systems varies from implementation to implementation.
  • Often depends on the capability of the systems with which it integrates (see discussion of open APIs earlier in this document).
  • Information presented in the portal is generally read-only, so changes still need to be made in the relevant clinical system (possibly via a “click-through”).
  • Each clinical system exposed via the portal is an individual point-to-point interface, so it is unlikely to scale beyond a single organisation or small number of local services.