Why the EEPD?
EEPD Structure
Slide Shows
Publicity Flier
Help Please
New Words and Concepts
I.  Discussion Topics
 II.  Nightmares!
 III.  Datasets(>80)
 IV.  Data Resource
 V.  Logical Priority
VI.  Perinatal RIOs
VII.  Prognosis
VIII.  Signposts
IX.  Leaflet Lists & Links
 X.  Whiteboards
 XI.  Casenotes
XII. Proformas (inc. Gyn)
XIII. Computer Printouts
XIV. Care Paths
XV. S.IN.B.A.D s
XVI. Questionnaires
XVII. Codes
XVIII. Audit Benchmarking
XIX. Filofaxes Mnemonics
XX. Anecdotal Evidence
XXI. Training
XXII. Organisation
XXIII. Equipment
XXIV. Leaflets (inc. Gyn)
XXIV. Safe Motherhood
XXVI. Neonatology
XXVII. Gynaecology
A. Initiatives
B. Related WEB sites
C. Commercial IT
D. IT Contracts
E. IT Programs
F. Publications
G. Contacts
RISCOS essential
About R Fawdry
Feedback
EPR News
Acknowledgements
Web Design

 

 

 
Reason for the EEPD
 
“Analysable and linkable Electronic Patient Records (EPRs) will only attain their true potential for improving the quality of patient care and reducing the risk of human error, without excessive data re-entry overload, when, in each speciality and sub-speciality - following intense, open, web-based discussions - their detailed, logically and chronologically-arranged, flow-patterned questions and the full range of all allowable answer-options - [always including, whenever needed, “Unknown (Free Text)” and “Other (Free Text)”] - are, by stages, taking into account as many interested parties as possible, individual question by individual question, internationally standardised.”
 
Such specifications will only become universally standardised if they are (a) created by hundreds of hours of work by health care professionals, since only they have the professional knowledge required for this task, and (b) are open-source and cost free to all potential users.
 
For the main slideshow presentation click “Why the EEPD?”  
or jump straight to “What the EEPD is”
 
In essence the EEPD, EEPDwiki and EEPDtalk are a long term attempt to bring together in these three websites all that is needed for the development of Shared Hospital/Community Perinatal Care Electronic and Paper IT Systems using an “Open Source”, “Joined up” and, in time, also a increasingly ”Wiki ” approach. Modifying the words of the Wikipedia commitment ”Imagine a world in which every single designer of a healthcare computer system can freely share in the sum of all the knowledge required for such an enterprise”
 
To see the wiki version at www.eepdwiki.org.uk
                                                       and see also the discussion forum at www.eepdtalk.org.uk
 
A Blueprint for similar shared-care specialities?
 
Essential Bedrock Foundation
 
Despite a widespread belief (slowly fading?), even among highly trained professionals, that computers are magic; both on financial and on technical grounds, it is, in practice, impossible to adequately integrate large flow-patterned analysable databases. Once they have been fully installed, it is virtually never cost-effective to write all the software code which is essential for adequate interoperability. 
 
Numerous examples confirm that a toxic combination of gullible managerial purchasers and plausible IT sales salesmen results time and time again, in projects disastrously over-running in time and cost, with an eventual failure to provide a viable inter-operative system at all. 
 
Confidential commercial competition for example has no place in the creation of the question and answer options used in the software required for fully functioning electronic analysable patient records.  The most vital open-access part of the EEPD is therefore:
(Updated 2 October 2012)
 

 

Email:

 

 
The EEPD by Dr. Rupert Fawdry is licensed under the Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Unported License. To view a copy of this license, visit http://creativecommons.org/licenses/by-nc-sa/3.0/. Permissions beyond the scope of this license are available via http://eepd.org.uk/?page_id=56.
Website Development by NOS Web Services