Taking his IT expertise from educational research, Mark transferred this to developing clinical laboratory transaction and record-keeping systems. He was effectively the sole author of the Phoenix/Achilles system which ran the Middlesex Hospital Clinical Chemistry laboratory for over 10 years. A succession of major analysers were interfaced to Phoenix/Achilles, of which the most complex (Vickers M300) was published.   

M.D.Buckley-Sharp (1972), Data Processing and Computers in Clinical Pathology.	A personally published book reviewing the systems then being considered by the Department of Health for widespread national implementation. Subsequently, the Department cancelled its national programme support, and one of the reviewed systems was developed independently into the Phoenix system. [No abstract]
V.M.Eldridge, M.D.Buckley-Sharp (1982), Data processing of the output from a Vickers M300 clinical chemistry analyser. Computer Programs in Biomedicine, 14, 213-224.	Our system to recover logging data from the M300 analyser, correct for any mechanical problems on the analyser, and transfer patient results into the Phoenix/Achilles laboratory information system on a Data General NOVA computer. [Complete paper]
M.D.Buckley-Sharp, V.M.Eldridge (1984). Phoenix/Achilles System Release 5, PAG, Introductory Guide.	This guide summarised the features of Phoenix/Achilles for new and prospective users, and was the first part of the fully comprehensive documentation prepared on the system after it had been running for several years. All the documentation was also printed on microfiche. [No abstract]
M.D.Buckley-Sharp, V.M.Eldridge (1984). Phoenix/Achilles System Release 5, PAS, System Programming Manual.	Provided detailed information to the system manager on setting up and using Achilles. This included advice on the generation of RDOS and Business BASIC as well as installing and configuring the Achilles system. [No abstract]
M.D.Buckley-Sharp, V.M.Eldridge (1984). Phoenix/Achilles System Release 5, PAPR, Program Specification Manual.	A detailed description of the specification of each program provided with the core Achilles system. Cross references were provided to other programs, and to data files used by each program. [No abstract]
M.D.Buckley-Sharp, V.M.Eldridge (1984). Phoenix/Achilles System Release 5, PAF, Data File Specification Manual.	A detailed description of each data file defined within the core Achilles system. Cross-references were provided to the programs using each data file. [No abstract]
M.D.Buckley-Sharp, V.M.Eldridge (1984). Phoenix/Achilles System Release 5, PAX, Analyser Suite and Additional Programs.	The manual described the ‘suites’ system included with the core Achilles system to help with writing specific software for particular analysers. Certain miscellaneous calculation programs were described. At any one time, the manual would also include specifications of programs and data files currently supported for particular analysers. [No abstract]
M.D.Buckley-Sharp, V.M.Eldridge (1984). Phoenix/Achilles System Release 5, PAOP, System Operator’s Manual.	The manual described the tasks required of the system operator. Critical tasks were described in an action format so that they could be followed as a method sheet. [No abstract]
M.D.Buckley-Sharp, V.M.Eldridge (1984). Phoenix/Achilles System Release 5, PAU, Terminal User’s Manual.	The manual described Achilles in simple terms for the general user. The normal use of the computer and the commonly used programs in Achilles were described. Each installation would include its own lists of wards, consultants, codes, tests and comments.  These code lists were published as frequently updated companion booklets. In our experience this averaged annually with 9 major editions from 1979 to 1988, and amendments in between. [No abstract]
M.D.Buckley-Sharp, V.M.Eldridge (1984). Phoenix/Achilles System Release 5, An Evaluation using the S.E.Thames RHA Questionnaire.	The questionnaire was designed for completion by potential system purchasers. It allowed them to assess individual systems for their features and usability. We self-assessed the Phoenix/Achilles system against this questionnaire. [No abstract]