CPOE の導入は投薬過誤の減少による安全確保を目的とし，その基本構造は，1）最善の医療行為に限定した迅速 な治療，2）病状変化への頻回な指示切り替え，3）数日後の治療を前提とした入力不要，4）成熟度，体重，病態の 多様性に対応，5）直感的，統一されたインタフェースと臨床診断意思決定支援システムの装備，6）チームでの治 療経過の共有，7）医事会計ではなく医学的データを優先，以上の救急部門情報システムの特性を模範としたい。必 要な機能は，1）/kg 計算と丸め，2）希釈，混注指示，3）輸液路管理，4）繊細な水分，電解質，栄養と血糖，黄 疸の管理機能と搾母乳データベースの装備である。薬剤部との交信は閉回路電子投薬管理による投薬過誤の排除の ために標準化される必要がある。
The structural concept for the NICU CPOE, which is to be implemented with the aim of improving safety through mitigation of medication errors, should have the following features as an emergency department information system（ EDIS）： 1）provides prompt delivery of information for safe and efficient patient care, 2）allows frequent ordering adjustments to meet the dynamic variability of patients’ conditions, 3）no need for data entry for assumed subsequent treatments, 4） adaptable to the diversity and complexity of patients, 5）provides an intuitive unified user interface and advanced clinical decision support system（ CDSS）, 6）enables sharing of clinical courses among team members in a shift-work setting, and 7）allows assignment of high priority to clinical data, but not to administrative data.
The functional requirements for accurate treatments are 1）specification of weight-based dosage with rounding calculation, 2）precise reconstitution drug or infusion management, 3）illustrative infusion route management, and 4）sophisticated fluid, electrolytes, and nutrition balance management, along with blood sugar and bilirubin management. Another requirement is the incorporation of an expressed breast milk （EBM） database within the default NICU CPOE, which is likely to improve the quality of care by providing meticulous balance management of EBM stocks and sharing of this information among staff. Digital data communication regarding medication between the NICU CPOE and the hospital pharmacy service system should be also a requirement for the default NICU CPOE to eradicate medication errors as a closedloop electronic medication management（ EMM） system.
