Karinoya Learning Room

Qualifications · Healthcare Information Technologist Success Lab

System Implementation and Operation

Read the questions and explanations in English. The lectures (explanatory articles) are available in Japanese only.

View the Japanese version (with lectures) →

Q1 | Life cycle

Which is a correct description of the life cycle of an information system?

  1. It refers to the continuous flow from planning and procurement through implementation, operation, and evaluation to the next upgrade
  2. Once a system is introduced, it never needs to be upgraded afterward
  3. The life cycle is a term that refers only to the useful life of the hardware
  4. The results of evaluations made during operation need not be reflected in the plan for the next system
AnswerA. It refers to the continuous flow from planning and procurement through implementation, operation, and evaluation to the next upgrade

An information system has a life cycle running from planning and procurement to implementation, operation, evaluation, and the next upgrade, and it is important to reflect evaluations made during operation in the plan for the next system. Implementation is not a one-time event, and the term does not refer only to hardware's useful life. The option that ignores evaluation results also contradicts the life cycle concept.

Q2 | RFI and RFP

Which is a correct description of an RFP (request for proposal)?

  1. A document asking vendors to provide information about their products and technologies
  2. A detailed design document that the vendor prepares after the contract is signed
  3. A document in which a vendor presents only an estimated price to the healthcare institution
  4. A document in which the healthcare institution states its requirements and asks vendors to submit proposals
AnswerD. A document in which the healthcare institution states its requirements and asks vendors to submit proposals

An RFP (Request for Proposal) is a document in which the healthcare institution states its requirements and procurement conditions and asks vendors to submit proposals. A document asking for product and technology information is an RFI (request for information), used at the stage before requirements are fixed. A price-only quotation or a post-contract detailed design document is not an RFP.

Q3 | Procurement steps

Which is the correct chronological order of steps for procuring a hospital information system?

  1. Issue the RFP → clarify procurement requirements → create vendor evaluation criteria → select the supplier and contract
  2. Select the supplier and contract → issue the RFP → clarify procurement requirements → create vendor evaluation criteria
  3. Create vendor evaluation criteria → select the supplier and contract → issue the RFP → clarify procurement requirements
  4. Clarify procurement requirements → create vendor evaluation criteria → issue the RFP → select the supplier and contract
AnswerD. Clarify procurement requirements → create vendor evaluation criteria → issue the RFP → select the supplier and contract

Procurement first clarifies the requirements, then studies the procurement method and creates vendor evaluation criteria, then prepares and issues the RFP, and finally evaluates proposals to select the supplier and contract. An order in which the RFP precedes requirement clarification, or the contract comes first, is impossible. The key point is that evaluation criteria are prepared before the RFP is issued.

Q4 | Requirement specification

Which is a correct description of a requirement specification?

  1. A document that contains the program source code as-is
  2. A document in which the healthcare institution clarifies the requirements it wants realized and conveys them to vendors
  3. A document defining procedures for handling failures that occur after the system goes live
  4. A completion report that the vendor submits to the healthcare institution when the system is delivered
AnswerB. A document in which the healthcare institution clarifies the requirements it wants realized and conveys them to vendors

A requirement specification is a document in which the healthcare institution clarifies the requirements it demands of the system and conveys them to vendors for procurement. It describes basic requirements, hardware and software technical requirements, inter-system connection requirements, and so on. A delivery completion report, source code, and failure response procedures are not requirement specifications.

Q5 | Vendor selection

Which is the most appropriate practice for making vendor selection fair and objective?

  1. Create vendor evaluation criteria before issuing the RFP and compare proposals against them
  2. Give only a particular vendor requirements more detailed than the RFP and let it propose
  3. Do not evaluate at all, and always choose the vendor with the lowest quoted price
  4. Wait until all vendors' proposals have arrived, then create evaluation criteria to fit their content
AnswerA. Create vendor evaluation criteria before issuing the RFP and compare proposals against them

Creating the evaluation criteria before issuing the RFP allows proposals to be compared fairly and objectively against the same yardstick. Making criteria after seeing proposals invites arbitrary evaluation. Selecting on price alone ignores functionality and maintenance capability, and giving extra information to a particular vendor undermines fairness, so those practices are inappropriate.

Q6 | Contract types

Which is a correct statement about ways of procuring equipment?

  1. In a lease, the healthcare institution purchases the equipment directly and books it as its own asset
  2. Purchased equipment carries no risk of obsolescence from technological progress
  3. A lease assumes long-term use and, as a rule, cannot be cancelled mid-term
  4. A rental assumes long-term use and, as a rule, cannot be cancelled mid-term
AnswerC. A lease assumes long-term use and, as a rule, cannot be cancelled mid-term

A lease is an arrangement in which equipment purchased by a leasing company is borrowed long-term and, as a rule, cannot be cancelled mid-term. A rental is for short-term use and can be cancelled mid-term, which distinguishes it from a lease. In a lease it is the leasing company, not the healthcare institution, that purchases and books the equipment. Purchased equipment becomes the institution's asset but cannot avoid the risk of obsolescence from technological progress.

Q7 | Outsourcing vs. dispatch

Which is a correct statement about the difference between outsourcing contracts and temporary staffing?

  1. In outsourcing, the ordering healthcare institution directly supervises and directs each of the contractor's workers
  2. In outsourcing, the contractor carries out the work under its own direction, while in temporary staffing the client site directs the workers
  3. There is no difference in the right of direction between the two; only the name of the contract differs
  4. In temporary staffing, the staffing agency supervises and directs the daily work at the client site
AnswerB. In outsourcing, the contractor carries out the work under its own direction, while in temporary staffing the client site directs the workers

Outsourcing is a contract in which the contractor carries out the work under its own responsibility and direction; the ordering healthcare institution cannot directly supervise the contractor's workers. In temporary staffing, the client healthcare institution directs the dispatched workers. Where the right of direction lies is the essential difference between the two — it is not merely a difference of name.

Q8 | Maintenance contracts

Which of the following is the most appropriate subject of a software maintenance contract?

  1. Replacing and repairing failed parts in the server itself
  2. Laying and wiring cables for the in-house LAN
  3. Relocation work when a terminal's installation site changes
  4. Fixing defects discovered after the system goes live
AnswerD. Fixing defects discovered after the system goes live

Software maintenance covers fixing defects (bugs) discovered after go-live and applying program corrections. Replacing or repairing server parts is hardware maintenance. Laying LAN cables and relocating terminals are construction and installation work, outside the scope of a software maintenance contract.

Q9 | Connection requirements

Which is the most appropriate description of inter-system connection requirements written in a requirement specification?

  1. Connection details can be decided after go-live, so they need not be written in the requirement specification
  2. Connection requirements are decided freely by each vendor, and the healthcare institution is not involved
  3. Clearly state the systems to be connected, the information to be exchanged, and the connection method, including use of standards
  4. If the products are from the same vendor, connection requirements need not be written
AnswerC. Clearly state the systems to be connected, the information to be exchanged, and the connection method, including use of standards

To connect multiple systems, such as the electronic medical record and departmental systems, the requirement specification must clearly state the systems to be connected, the kinds of information to be exchanged, and the connection method (including use of standards), and clarify the scope of responsibility. Deciding after go-live, leaving it to vendors, or skipping it for same-vendor products invites connection failures and unclear accountability.

Q10 | Healthcare CIO

Which is the most appropriate statement about the strategy for implementing a hospital information system?

  1. The purpose of system implementation is limited to making clerical work more efficient
  2. Once the implementation strategy is decided, no subsequent evaluation or review is considered necessary
  3. The implementation strategy should be formulated by the IT department alone, without involving management or clinical departments
  4. The implementation strategy is formulated based on the hospital's management strategy, with the healthcare CIO playing the central role in promoting the IT strategy
AnswerD. The implementation strategy is formulated based on the hospital's management strategy, with the healthcare CIO playing the central role in promoting the IT strategy

Implementing a hospital information system is part of an IT strategy based on the management strategy; management involvement and consensus-building are essential, and the chief information officer for healthcare (healthcare CIO) leads the planning and promotion of the strategy. Deciding within the IT department alone lacks consensus. Purposes have diversified to include improving quality of care and cooperation, and the strategy must be repeatedly evaluated and revised.

Q11 | Master data creation

Which is the most appropriate statement about creating master data at implementation?

  1. Master data creation can start after the system goes into service
  2. Because vendors supply standard masters for drugs, disease names, and so on, the healthcare institution need not be involved at all
  3. Masters for drugs, disease names, test items, and so on depend heavily on in-house operations, so the healthcare institution's involvement is essential
  4. Once master data has been created, it never needs review or updating
AnswerC. Masters for drugs, disease names, test items, and so on depend heavily on in-house operations, so the healthcare institution's involvement is essential

Masters for drugs, disease names, test items, users, and so on depend heavily on the institution's actual circumstances, such as the drugs it stocks and its operating rules, so the healthcare institution must take an active role in preparing them. They cannot be left to the vendor, and the system will not work correctly unless they are ready before go-live. Masters also require continuous management after go-live, for example to track drug price revisions.

Q12 | Implementation order

Which is the correct order of work from the implementation phase to the start of service?

  1. Master data creation → detailing operations and specifications → acceptance → operational test (rehearsal)
  2. Detailing operations and specifications → master data creation → operational test (rehearsal) → acceptance
  3. Acceptance → detailing operations and specifications → master data creation → operational test (rehearsal)
  4. Operational test (rehearsal) → detailing operations and specifications → acceptance → master data creation
AnswerB. Detailing operations and specifications → master data creation → operational test (rehearsal) → acceptance

The implementation phase proceeds through detailing operations and specifications, development, configuration and system construction, master data creation, system testing, data migration, and user training; an operational test (rehearsal) is performed before go-live, and service begins after acceptance. Orders in which acceptance or the rehearsal precedes detailing specifications or master creation do not hold up.

Q13 | Data migration

Which is the most appropriate statement about migrating data from the old system to the new system?

  1. Decide the scope of data to migrate, and verify after migration that the data was carried over correctly
  2. Data migration can be done slowly after the start of service, so no pre-go-live planning is needed
  3. No verification of the migrated data is necessary
  4. Discard all data from the old system and carry nothing over to the new system
AnswerA. Decide the scope of data to migrate, and verify after migration that the data was carried over correctly

In data migration, it is important to decide which parts of the basic patient information and clinical data to migrate, study the migration method, carry it out, and then verify that the data was carried over correctly. To maintain continuity of care it must be planned and done before go-live; skipping verification or discarding clinical data without carrying it over is inappropriate.

Q14 | Acceptance

Which is a correct description of acceptance (kenshū)?

  1. Analyzing the causes of failures that occurred after go-live
  2. The vendor runs unit tests on the programs in-house to confirm quality
  3. The healthcare institution confirms that the delivered system works as specified in the requirements and accepts it
  4. The healthcare institution runs operation training sessions for its staff
AnswerC. The healthcare institution confirms that the delivered system works as specified in the requirements and accepts it

Acceptance is the act by which the ordering healthcare institution confirms that the delivered system works as specified in the requirements and accepts it; delivery is complete upon acceptance. The vendor's in-house unit tests are part of system testing, operation training is user education, and failure cause analysis is an operations-phase activity; none of these is acceptance.

Q15 | Rehearsal

Which is the most appropriate purpose of the operational test (rehearsal)?

  1. Estimating the effort and cost the vendor needs for development
  2. Measuring the cooling capacity of the air conditioning installed in the server room
  3. Using the system end to end along the actual workflow to uncover operational problems before go-live
  4. Visually checking the developed program's source code 1 line at a time for errors
AnswerC. Using the system end to end along the actual workflow to uncover operational problems before go-live

The operational test (rehearsal) uses the system as in production, following the actual workflow from reception through consultations, tests, and payment, in order to uncover operational problems before go-live. Source code review is developer-side testing, effort estimation belongs to the procurement and contract stage, and measuring air conditioning capacity is a facilities matter, not the purpose of the operational test.

Q16 | Consensus building

Which is the most appropriate purpose of setting up working groups with frontline staff during system implementation?

  1. To detail each department's operations and specifications and build consensus within the hospital
  2. To make decision-making procedures by management unnecessary
  3. To reduce IT department staff and cut costs
  4. To keep the contract price with the vendor secret from other staff in the hospital
AnswerA. To detail each department's operations and specifications and build consensus within the hospital

Working groups bring together frontline representatives — physicians, nurses, technologists, clerical staff — to detail each department's operations and specifications, reconcile requests, and advance consensus within the hospital. Their purpose is not to hide the contract price, nor to replace decision-making by management (such as committees), nor to serve as a staff-reduction measure.

Q17 | Vendor structure

Which is the most appropriate description of the vendor-side structure in an implementation project?

  1. The vendor's staff assignments need not be decided even after the contract is signed
  2. No project structure is formed on the vendor side; a single sales representative handles every phase
  3. The vendor's structure is internal information and must not be disclosed to the healthcare institution
  4. A structure is formed around a project manager, with staff in charge of design, development, and implementation support
AnswerD. A structure is formed around a project manager, with staff in charge of design, development, and implementation support

On the vendor side, a project structure is formed around a project manager with staff for design, development, and implementation support, coordinating with the corresponding structure at the healthcare institution. A single sales representative does not handle every phase. The structure is presented to the institution in proposals and the like, and assigning staff is also necessary to keep the coordination contact points clear.

Q18 | Coordination

Which is the most appropriate description of coordination when multiple vendors are involved in implementing a hospital information system?

  1. Establish in advance mechanisms for coordination between organizations within the hospital, between the hospital and vendors, and among the vendors themselves
  2. Coordination should as a rule be done orally only, with nothing left in writing
  3. Departmental system vendors must not share connection specifications with one another
  4. Decide that no vendor will coordinate with the others, and think about a response only after problems arise
AnswerA. Establish in advance mechanisms for coordination between organizations within the hospital, between the hospital and vendors, and among the vendors themselves

In implementations involving multiple vendors, such as the electronic medical record and departmental systems, it is important to establish in advance mechanisms — such as coordination meetings — for coordination between organizations within the hospital, between the hospital and vendors, and among the vendors. Ad hoc responses after problems occur and refusing to share connection specifications invite connection failures. Coordination outcomes should be recorded and shared.

Q19 | Go-live support

Which is the most appropriate response immediately after the start of service?

  1. Decide not to respond to contacts from the frontline during the period just after go-live, even if failures occur
  2. Temporarily suspend all staff accounts to avoid confusion
  3. Erase all data from the old system immediately when the new one goes live
  4. Vendor and IT department staff stand by on site and respond immediately to questions and problems
AnswerD. Vendor and IT department staff stand by on site and respond immediately to questions and problems

Immediately after the start of service, operation questions and problems tend to concentrate, so vendor and IT department staff stand by on site and respond immediately (go-live support). Refusing to respond to failures, suspending accounts right after go-live, and immediately erasing the old system's data would undermine continuity of care and data preservation, and are inappropriate.

Q20 | Purpose of adoption

Which is the most appropriate statement about the purposes of implementing a hospital information system?

  1. The purpose of system implementation need not be clarified before preparing the requirement specification
  2. The sole purpose of system implementation is to enable prompt health insurance claims
  3. The purpose of system implementation is to increase the IT department's workload and expand its organization
  4. Beyond work efficiency, purposes have diversified to include improving quality and safety of care and regional cooperation
AnswerD. Beyond work efficiency, purposes have diversified to include improving quality and safety of care and regional cooperation

The purposes of implementing a hospital information system have diversified beyond clerical efficiency and insurance claims to include improving the quality and safety of care, use in management, and support for regional cooperation. Clarifying the purpose is a precondition for writing the requirement specification and for post-implementation evaluation; implementing without defined purposes, or reducing the purpose to a single item, is not appropriate.

Q21 | 3 layers of rules

In the 3-layer structure of information system operating rules, which one states the organization's basic policy?

  1. Manifesto
  2. Policy
  3. Procedure
  4. Standard
AnswerB. Policy

Operating rules are organized in 3 layers: the policy stating the basic principles, the standard — the operating management regulations that make it concrete — and the procedures defining day-to-day work steps. Procedures are at the manual level and standards at the regulation level, not the basic policy. "Manifesto" is not a term in this 3-layer structure.

Q22 | Regulation items

Which of the following is not an appropriate item to include in a hospital information system's operating management regulations?

  1. Provision of education and training
  2. Safety measures for outsourced work
  3. A list of individual patients' diagnoses
  4. Users' responsibilities
AnswerC. A list of individual patients' diagnoses

Operating management regulations define the objects and structure of management, the responsibilities of administrators, responsible persons, and users, the use of servers, terminals, and networks, data handling and storage, education and training, safety measures for outsourced work, penalty provisions, and so on. A list of individual patients' diagnoses is the content of clinical records and does not belong in regulations that set operating rules.

Q23 | User management

Which is the most appropriate user management for a hospital information system?

  1. Post passwords on the terminals so everyone knows them
  2. Suspend retirees' accounts promptly
  3. Share 1 ID among everyone in a department
  4. Keep retirees' accounts valid forever as a memento
AnswerB. Suspend retirees' accounts promptly

In user management, account registration and suspension should be linked with personnel information, and the basic rule is to suspend retirees' accounts promptly. Sharing IDs makes the record of who did what (the audit trail) meaningless, and leaving retiree IDs active or posting passwords invites unauthorized access; all of those are inappropriate.

Q24 | Segregation of duties

Which is the most appropriate description of the principle of segregation?

  1. The idea of separating authority and duties so they are not concentrated in 1 person and mutual checks can work
  2. The idea of painting terminals different colors for each clinical department to tell them apart
  3. The idea of giving every user identical administrator privileges so anyone can perform the same operations
  4. The idea of unifying passwords across all staff and sharing them
AnswerA. The idea of separating authority and duties so they are not concentrated in 1 person and mutual checks can work

The principle of segregation separates authority and duties instead of concentrating them in 1 person — for example, having registration and approval done by different people — so that mutual checks prevent fraud and mistakes. Giving everyone administrator privileges and unifying passwords run counter to safe management. Color-coding terminals has nothing to do with segregation of duties.

Q25 | Master maintenance

Which is the most appropriate handling of the master entry for a drug the hospital has stopped stocking?

  1. Do nothing in particular, leaving it selectable in new orders
  2. Physically delete the entry from the master
  3. Rewrite the entry's name to another drug's name and reuse it
  4. Deactivate (suspend) it without deleting, preserving consistency with past data
AnswerD. Deactivate (suspend) it without deleting, preserving consistency with past data

Deleting a master entry makes past transaction data that references it (such as prescription histories) impossible to display correctly. To preserve consistency between the master and transaction data, the entry is deactivated (suspended) rather than deleted. Rewriting the name changes the meaning of past records, and doing nothing invites erroneous orders.

Q26 | Failure response

Which is the most appropriate response when the hospital information system stops during clinical care?

  1. Assess the scope of impact, notify the affected departments, and switch to alternative operation such as paper procedures
  2. Do not contact the user departments at all until the cause of the failure has been determined
  3. Proceed with recovery work without telling anyone in the hospital that a failure has occurred
  4. Suspend all care and wait until the system is restored
AnswerA. Assess the scope of impact, notify the affected departments, and switch to alternative operation such as paper procedures

In a system failure, assess the scope of impact, promptly notify the user departments, and switch to predefined alternative operation such as paper procedures so care can continue. After recovery, the records made during alternative operation are entered retroactively. Suspending all care undermines continuity of care, and doing recovery work without notification leaves the frontline unable to judge the situation and causes confusion.

Q27 | IT-BCP

Which is the most appropriate statement about IT-BCP and disaster recovery?

  1. IT-BCP is a plan for continuing critical operations even in a disaster, and disaster recovery refers to restoring the damaged systems
  2. Disaster recovery refers to the set of procedures for procuring and replacing a new information system
  3. If an IT-BCP has been drawn up, drills for disasters are unnecessary
  4. IT-BCP is a plan for advertising and publicity conducted in normal times
AnswerA. IT-BCP is a plan for continuing critical operations even in a disaster, and disaster recovery refers to restoring the damaged systems

IT-BCP, as part of business continuity management in a healthcare facility, is a plan for continuing and quickly resuming critical operations even during disasters and failures, while disaster recovery refers to restoring and rebuilding the damaged information systems. It is important not only to draw up the plan but to run drills in normal times in preparation; it is not about procurement procedures or advertising.

Q28 | System modification

Which is a representative system modification that arises regularly during the operation phase of a hospital information system?

  1. Handling revisions of parking fees
  2. Handling revisions of the medical fee schedule
  3. Handling menu changes in the staff cafeteria
  4. Handling a change of the hospital's logo
AnswerB. Handling revisions of the medical fee schedule

A representative system modification in the operation phase is handling revisions of the medical fee schedule (診療報酬改定). Each revision requires modifying the masters and calculation logic of the billing and order entry systems. Modifications for patient safety are also cited as typical. Logos, cafeteria menus, and parking fees are not representative modifications of a hospital information system.

Q29 | Continuous improvement

Which is the most appropriate flow of continuous improvement for a hospital information system?

  1. Define what to measure, collect and analyze data, compile the information, and connect it to corrective actions
  2. Only collect data, without analyzing or using it
  3. Proceed by first carrying out corrective actions and then defining what to measure and how
  4. Make no improvements, giving top priority to maintaining the status quo
AnswerA. Define what to measure, collect and analyze data, compile the information, and connect it to corrective actions

Continuous improvement starts by defining what to measure and confirming it can be measured, then proceeds through data collection, processing and analysis, and compiling and using the information, leading to corrective actions. Corrective actions never come first, and without analyzing the collected data there is no basis for improvement. Prioritizing the status quo contradicts the idea of continuous improvement.

Q30 | Side effects

Which of the following is cited as a side effect of implementing hospital information systems and digitalization?

  1. Introducing a system always cuts the hospital's electricity use in half
  2. Confusion caused by partial loss of communication and changes in workflow
  3. The number of handwritten documents used in the hospital increases with digitization
  4. The legibility of clinical records declines greatly compared with paper records
AnswerB. Confusion caused by partial loss of communication and changes in workflow

Side effects of digitalization include partial loss of communication as more exchanges happen through screens, confusion from workflow changes, confusion in operations during failures, and inappropriate stereotyping of care through templating. Digitization actually improves legibility and reduces handwritten documents. Halving electricity use has nothing to do with the side-effect discussion.

Practice: answer the questions on this page

This practice tool asks questions in random order (it works when JavaScript is enabled). You can still read all the questions and explanations above without it.

* The explanations are information for study purposes. Exam scope and systems change from year to year, so always check the official announcements of the organization that administers the exam.

This page is a translation of the Japanese original. If the translation and the original differ, the Japanese version takes precedence. View the Japanese original