Data Imports

  • Once the data is imported from your old, antiquated system onto the newer, better MediFacts, the MediFacts staff will examine the imported data for reasonableness and completeness and will adjust the data accordingly or notify you that certain fields were not carried on your old system.


  • Training will begin with a hands-on teaching session with your employees, actually using the live system with pseudo test patients, about how to enter or review patient demographics, insurance, appointments, facility scheduling, schedule printing, and where to obtain help.

  • During this session MediFacts will also be making sure system permissions, office hours, on screen color coding, etc are correctly set and correcting any anomalies on the spot. Personnel from our programming staff will be on call during this session in the event situations the trainer has never seen before arise so that training can continue apace.

  • At this point in the training MediFacts would encourage your front desk people to begin setting up a few of the first day of operation patient appointments, etc.

  • Normally at this point MediFacts steps back, but just a phone call away with frequent follow-ups, and lets you and your employees work with the system.

  • The next training session would take place as soon as you and your staff are ready and would center on answering questions that have come up about the system, coaching on more efficient ways to use the system, the scanning of intake packets on to the system, and attaching those scanned documents in an organized manner to the patient. For an ASC, the session would also include the creating of patient oriented forms and labels to streamline ASC operation. 


  • Invariably at this point the light bulb goes off and someone says “Does this mean we can go paperless”. The answer is yes with the codicil that some original signed forms must be kept on record for legal reason.

  • Normally at this point MediFacts steps back, but just a phone call away with frequent follow-ups, and lets you and your employees work with the system.

  • Training for the billing people would be handled in a similar manner

  • Training for ASC personnel would be handled with addition training on the inventory, physical facilities management, management reports, and regulatory reporting modules as required.

  • Physician training on those parts of the system containing monetary data that can be only viewed by the practice or facility owner or specifically designated employees can begin when there is data to be reviewed.

  • As MediFacts becomes a part of your way to do business there will be questions. We are available 24/7 at a number provided to you to answer questions and most find our help screens useful.

  • MediFacts is not a static system. Driven by customer feedback, regulatory events, and our internal vision, Medifacts is constantly changing. Our change process is controlled.

  • MediFacts has a whole dedicated module to securely manage the change process. Any one requesting a change

         to MediFacts uses our Program Change Request (PCR) system. No changes are made without an approved PCR.

  • Generally the system works like this: a change request is generated by the customer communicating the exact needed change to the account’s MediFacts customer executive. Together they work out and enter into a standard PCR form the details the programmer needs to know, the expected outcome of the change, the business reason for the change, and any timing concerns.  The PCR request submission is stored on the system for approval by The MediFacts CIO or his designated proxy.

  • As the PCR passes through the construction phase each step is tracked so we know the current status at any point in time. Once programming is complete the PCR is implemented on our separate stand alone “Test System” for quality control by the customer, programmers, and other interested parties. The customer receives an email with testing instructions if required. 


  • No changes go into production without passing quality control.

  • When the PCR meets the customer’s needs, the MediFacts CIO or his designated proxy approves the change to the production system. When the PCR code is installed on the production system the customer is notified.


  • If after initial installation on the production system, additional changes are required the PCR is marked “Customer Rework” and returned to the programmer.


  • Once the change has been working on the system with no apparent errors the PCR is closed by the CIO.


  • We gather time based process metrics throughout the change process so we can get better.