Date: Fri, 29 Mar 2024 07:49:14 +0000 (UTC) Message-ID: <1042467238.55.1711698554547@74cc45a591cd> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_54_1219561420.1711698554547" ------=_Part_54_1219561420.1711698554547 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
UK renal units started using computerised electronic patient rec= ords (EPRs) in the 1960s. Every adult renal unit in the UK now has a well-d= eveloped EPR system provided by a variety of third party software suppliers= .
These EPRs were deployed before standards had been developed. Many of th= ese systems were built with individual schemes for coding, commun= ication, naming conventions, definitions, error trapping and vali= dation. As a result some cannot support modern and now often mandatory proc= esses for security, patient identification, clinical coding (diagnoses and = procedures) or the use of granular hierarchical schemes that allow dat= a to be grouped automatically.
Few current systems can store the metadata which are required to in= terpret data correctly (e.g. assay method and reference range). It is also = impossible to transfer records electronically between renal units or other = specialities when a patient changes address or status. In some cases word o= f mouth and local knowledge are required to interpret the data and operate = the systems.
In recognition that better use could be made of existing knowledge, = ;collaborations, patient involvement and new information technologies, the = UK Renal Data Collaboration was formed at a meeting at The Royal Infirmary = Edinburgh on 29 Nov 2012.