diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Analysis/Index.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Analysis/Index.page.md new file mode 100644 index 00000000..696524d8 --- /dev/null +++ b/guides/Live-ImplementationGuide-BaRS/Home/Analysis/Index.page.md @@ -0,0 +1,5 @@ +--- +topic: Analysis +--- + +# {{page-title}} \ No newline at end of file diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Analysis/Infrastructure/Index.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Analysis/Infrastructure/Index.page.md index a3def039..3047bb26 100644 --- a/guides/Live-ImplementationGuide-BaRS/Home/Analysis/Infrastructure/Index.page.md +++ b/guides/Live-ImplementationGuide-BaRS/Home/Analysis/Infrastructure/Index.page.md @@ -2,4 +2,26 @@ topic: infrastructure --- -# {{page-title}} \ No newline at end of file +# {{page-title}} + +The infrastructure components defined as parts of BaRS are offered for use as a set of centralised services that can support workflows and simplify integration between systems. + +There are two elements to this infrastructure: + +- **a routing proxy** that enables systems to connect to each other in a scalable way that does not require each side to have pre-configured direct connections +- a set of enabling **discovery services** that allow BaRS clients to "discover" events, tasks and requests that have been made using BaRS compliant systems from a number of contexts + +The routing proxy is the main infrastructure component of BaRS and is hosted and maintained on the centralised NHS API Management platform. It is comprised of several components but, from a developer perspective, it can be thought of as a proxy. All requests are routed through it, it brokers the endpoint for a given service (on behalf of a Sender) and delivers the request to the Receiver. It can support both national and regional scale service service discovery tools. The BaRS Proxy supports scalable, dynamic interoperability and lowers the barrier of entry. This centralised infrastructure handles the burden of establishing endpoints and connectivity; a Sender need only communicate with the BaRS proxy and a Receiver only needs to accept requests from it. + +Components of BaRS centralised infrastructure are as follows: + +| Component | Description | +|-----------------------|--------------| +| BaRS Proxy API | Senders direct all requests to this Proxy API for all requests. | +| Endpoint catalogue | A component that holds service identifiers and their corresponding physical addresses. It is capable of supporting national and local directory of services or even standalone endpoints configured within a single system. Providers will be able to manag their endpoints via an API. | + + + + | + +
CAD to CAD Out of Area Referral
CAD to CAD Call Assist Request
CAD to CAD Mutual Aid Request | 1.0.0-beta.6 | API Spec v1.3.0 and above | {{pagelink:design-core-1.1.4, text:Core v1.3.0 and above}} |
+| {{pagelink:application6, text: Referrals into an Ambulance Service Trust (Application 6)}} |
CAD to CAD Out of Area Referral
CAD to CAD Call Assist Request
CAD to CAD Mutual Aid Request | 1.0.0-beta.7 | API Spec v1.3.0 and above | {{pagelink:design-core-1.1.4, text:Core v1.3.0 and above}} |
| {{pagelink:application7, text: Bookings into GP Practice (Application 7)}} |
Appointments for Patient facing services into GP Practice | 1.0.0-alpha.4 | API Spec v1.3.0 and above | {{pagelink:design-core-1.1.4, text:Core v1.3.0 and above}} | | {{pagelink:application8, text: Referrals into a broker for Healthcare Service selection (Application 8)}} |
Advice and guidance referring into electronic Referral Service (eRS) | 1.0.0-alpha | API Spec v1.3.0 and above | {{pagelink:design-core-1.1.4, text:Core v1.3.0 and above}} | @@ -176,8 +176,8 @@ Table detailing active versions of the latest Applications in Production (or cur