Post by account_disabled on Dec 8, 2023 23:29:09 GMT -5
Needs to be navigated for a new app to be successfully deployed which is where Blueberry can help due to our long experience in the field. The TLDR on NHS APIs Since medical app features can vary hugely from app to app how they access the NHS depends on what they do and the information they need to access. As a starting point any app that wants to access the NHS needs to integrate with the NHS Spine via one of their APIs there are in the NHS Digital API catalogue and connectivity is usually via an NHS Smart Card. The HSCN Health and Social Care Network connection and setting up of an ODS unique identification code for organisations that interact with any area of the NHS can also be complex areas to navigate.
For example HSCN connectivity requires setting up your servers behind a HSCN enabled server so that the application has access to the Spine services. It’s also important that the application supports multiple browsers Email Marketing List to access the required NHS services. This is not always trivial as each browser is different. Applications requiring access to patient data via the Personal Demographics Service PDS and Service Care Records SCR usually follow the steps: Creation of developer account > setting up the application so that it can access the right spine services > testing > integration.
The most complex part of the process of going live with a new application around steps is obtaining the technical conformance certificate from the NHS assurance team as it involves the process of completing the SCAL Supplier Conformance Assessment List technical document for both PDS and SCR so that they can provide the required sign off for the certificate to be issued. One of the criteria for SCAL approval is a successful Pen Test Penetrating testing across the NHS platforms to be used by the app.
For example HSCN connectivity requires setting up your servers behind a HSCN enabled server so that the application has access to the Spine services. It’s also important that the application supports multiple browsers Email Marketing List to access the required NHS services. This is not always trivial as each browser is different. Applications requiring access to patient data via the Personal Demographics Service PDS and Service Care Records SCR usually follow the steps: Creation of developer account > setting up the application so that it can access the right spine services > testing > integration.
The most complex part of the process of going live with a new application around steps is obtaining the technical conformance certificate from the NHS assurance team as it involves the process of completing the SCAL Supplier Conformance Assessment List technical document for both PDS and SCR so that they can provide the required sign off for the certificate to be issued. One of the criteria for SCAL approval is a successful Pen Test Penetrating testing across the NHS platforms to be used by the app.