Patterns
This section has been included to emphasise the use of design patterns in to the process of deciding how to use ITK3 Outpatient Letter within ITK3 Messaging Solutions. The information has been taken from developer.nhs.uk.
Overview
A “pattern” is a formal way of documenting a solution to a design problem in a particular field of expertise for example in the case of an ITK3 Messaging Solution sharing clinical information between systems. The information in this section has been reproduced and shortened from developer.nhs.uk
- Patterns are not mutually exclusive: many real solutions will use more than one pattern.
- Solutions may evolve from simpler to more complex patterns over time.
- Some patterns will be better for specific sharing needs than others – there is no “one size fits all”.
- Some patterns will scale better to larger populations.
- Some patterns require additional capabilities or services to be in place.
List of patterns
Below is a list of patterns. If you require more detail please go to developer.nhs.uk and click on the pattern for more information.
- Single Shared Application
- Portal
- Click Through
- Store and Notify
- Broadcast (Point to Point Sharing)
- Shared Repository
- Message Broker
- Registry Repository
- Publish Subscribe
Patterns and ITK3 Outpatient Letter Based ITK3 Messaging Solutions
Considering the design pattern / topology influences how any exposed ITK3 Outpatient Letter based ITK3 Messaging Solutions can be used and work within a system. ITK3 Messaging Solutions help to expose information to all design patterns allowing great user experiences to be created quickly, securely and consistantly.
