|
|
|
|
| LEADER |
01000naa a22002652 4500 |
| 001 |
NLM104963921 |
| 003 |
DE-627 |
| 005 |
20231222133639.0 |
| 007 |
tu |
| 008 |
231222s1999 xx ||||| 00| ||eng c |
| 028 |
5 |
2 |
|a pubmed24n0350.xml
|
| 035 |
|
|
|a (DE-627)NLM104963921
|
| 035 |
|
|
|a (NLM)10566401
|
| 040 |
|
|
|a DE-627
|b ger
|c DE-627
|e rakwb
|
| 041 |
|
|
|a eng
|
| 100 |
1 |
|
|a Abookire, S A
|e verfasserin
|4 aut
|
| 245 |
1 |
3 |
|a An institution-based process to ensure clinical software quality
|
| 264 |
|
1 |
|c 1999
|
| 336 |
|
|
|a Text
|b txt
|2 rdacontent
|
| 337 |
|
|
|a ohne Hilfsmittel zu benutzen
|b n
|2 rdamedia
|
| 338 |
|
|
|a Band
|b nc
|2 rdacarrier
|
| 500 |
|
|
|a Date Completed 01.02.2000
|
| 500 |
|
|
|a Date Revised 13.11.2018
|
| 500 |
|
|
|a published: Print
|
| 500 |
|
|
|a Citation Status MEDLINE
|
| 520 |
|
|
|a Clinical software can have a major impact on the delivery of care. It is imperative that clinical software undergo regular quality review, to evaluate the clinical correctness of the specification, the technical correctness of the software, problems that have arisen, and maintenance of the software as conditions change. We have developed a process using existing hospital review groups to perform clinical review, and using a project specification form and analysis of likely problem areas to effect technical review
|
| 650 |
|
4 |
|a Journal Article
|
| 650 |
|
4 |
|a Research Support, U.S. Gov't, P.H.S.
|
| 700 |
1 |
|
|a Teich, J M
|e verfasserin
|4 aut
|
| 700 |
1 |
|
|a Bates, D W
|e verfasserin
|4 aut
|
| 773 |
0 |
8 |
|i Enthalten in
|t Proceedings. AMIA Symposium
|d 1998
|g (1999) vom: 23., Seite 461-5
|w (DE-627)NLM098642928
|x 1531-605X
|7 nnns
|
| 773 |
1 |
8 |
|g year:1999
|g day:23
|g pages:461-5
|
| 912 |
|
|
|a GBV_USEFLAG_A
|
| 912 |
|
|
|a SYSFLAG_A
|
| 912 |
|
|
|a GBV_NLM
|
| 912 |
|
|
|a GBV_ILN_350
|
| 951 |
|
|
|a AR
|
| 952 |
|
|
|j 1999
|b 23
|h 461-5
|