Docstoc

Functional Requirements - San Mateo County.xls

Document Sample
Functional Requirements - San Mateo County.xls Powered By Docstoc
					                                    San Mateo Medical Center
                      Functional Requirements Vendor Response Instructions

Each functional requirement (FR) requires a response in the "vendor response" column.
Comments are optional.

Vendor Response Column

 Score   Definition
   3     Currently Available and Installed. A standard function/feature of the product that is in production
         use at multiple client sites, is demonstrable at those sites and does not require product modification to
         obtain.
   2     Available with Modifications. A standard function/feature that requires site-specific programming or
         customization (at a cost to the client) to achieve the requirement and which the vendor would be
         willing to provide if requested. Please quote additional cost.
   1     Under Development. A function/feature currently in developmental stages that is scheduled to
         become a standard capability within 12 months from the proposal date. Please state the scheduled
         availability date in the Comments column.
   0     Not Available. A function/feature that is not planned for development and is unable to meet the
         requirement. Any field left blank will be assumed to be “0=Not Available”.


Additional Cost Column
         For those items that require customization resulting in additional costs to the client. Note estimated
         cost in this column. Indicate if 3rd party software costs also.


Comments Column
         Each vendor is encouraged to provide module names and brief explanations or clarifications for any
         Functional Requirement question. Provide other annotations, and/or reference other sections of the
         proposal as needed.


Other Requirements
         All Functional Requirements must be returned in one Excel file – not PDF’d
         One response score per requirement. If the requirement is only partially met at this time, score it as a 1
         Limit the size of the comments to 200 characters; and only one cell of comments.
         Do not add rows anywhere in the spreadsheet – no headers or introduction materials, additional rows
         in the middle or the end
         Do not change the names of the tabs

                                                       Thank You !
Appendix F: 2. Hospital Based Core Clinicals


                                                                                         Vendor Response:
  NO.                      FUNCTIONAL REQUIREMENT                                                                                                    Comments
                                                                                             Availability
                                                                                            (3, 2, 1, or 0)   Est. Delivery Date   Additional Cost
        ORDER MANAGEMENT
        Order Processing
   1    System shows patient core data on order screen (i.e., height, weight,
        problem list, diagnosis, allergies, attending physician, etc.) with ability to
        drill down into history
   2    System shall provide capability for "Favorite Orders" folder by provider that
        do not require re-setup after system upgrades.
   3    System shall support orders templates with default values and pick lists to
        aid in order entry
   4    Orders can be entered directly from the clinical pathway/care plan
   5    System shall provide the ability to free-form miscellaneous orders
   6    System shall support all types of orders: such as, STAT, one time,
        recurring, continuing, corollary, pending, PRN, order sets, standing orders,
        serial etc.
   7    System shall support the use of conditional orders, as well as protocols
        and pathways
   8    System supports customizable prioritization of orders
   9    System supports special orders such as restraints, code status, etc. with
        accompanying documentation required (or prompts)
   10   System shall provide the ability to "hold" future orders and automatically
        change order when that future time arrives (i.e. NPO after midnight would
        be held in the system until midnight and the order would automatically
        change to NPO at midnight)
   11   System shall provide the ability to enter a future order in the ambulatory
        setting to be executed in the inpatient setting (e.g. pre-op order for ATB
        ordered during pre-surgical visit to be administered upon arrival to OR
        check-in)
   12   System shall support both "hold" and "resume/restart" mechanisms (e.g.,
        NPO, surgery, etc.) per JCAHO requirements
   13   System shall provide the ability for open-ended orders - i.e. ongoing
        treatment by Rehab after evaluation
Appendix F: 2. Hospital Based Core Clinicals
   14   System supports automatic generation of secondary orders that are
        prerequisites for or related to the entered order (e.g. Check digoxin levels
        every 3 weeks if Dig ordered) with ability to change/delete secondary order


   15   System shall provide the ability to place/view conditional discharge orders
        showing orders that have not been completed
   16   System shall provide the ability to work with multiple orders at one time,
        i.e. cancel or activate a group of orders and to allow unlimited orders within
        a department
   17   System shall provide the ability for orders to be backdated and marked as
        late entries, with the ability to set time limits for backdating and appropriate
        security to do so
   18   System supports orders that can be renewed per re-evaluation
   19   System shall have the capability to modify existing order and have the
        revisions highlighted. Alert pharmacy/ancillary/provider as appropriate.
   20   System shall have the ability to create an order from a similar existing
        order (e.g., duplicated for a future date and/or time)
   21   System shall provide the ability to view and update all previous orders
   22   System shall provide the ability to specify a stop/expiration date for select
        orders which is also editable 'on the fly' by the ordering physician, and
        automatically remove a stop date if user-defined criteria are met


   23   System supports a one-step process to cancel or discontinue an order
        during the order entry process, or once it has been ordered.
   24   System provides a prompt when discontinuing an order to verify the action

   25   Systems requires that medication orders are verified prior to administration.

   26   System provides the ability for user comment field on orders (i.e. special
        instructions and clinical ordering detail) that can be interfaced to an
        ancillary system if needed
   27   System supports the ability to discontinue and re-start orders based on
        specific criteria/alerts.
   28   System shall provide the ability for the user to define the inclusion of data
        elements in orders
   29   System shall provide the ability to enter medical necessity for the order
   30   System shall provide the ability to require justification for certain orders
   31   System shall provide the ability to document justification for not carrying
        out/completing an order
Appendix F: 2. Hospital Based Core Clinicals
   32   System shall have an order cancel reason that can be configured to be
        required or not required on order type or other parameters
   33   System shall provide the ability to alert AND redirect the provider when
        there is an error in the order
   34   System shall have the ability to selectively send reminders if order is not
        complete
   35   System supports alerts based on patient demographics; for example,
        insurance coverage
   36   System supports alerts to providers at time of order that insurance
        information is needed
   37   System shall provide the ability to define order-based alerts based on test
        and/or time intervals and/or patient coverage (i.e. ABNs)
   38   System shall provide the ability (as an option) to require signatures to be
        completed before another order is placed
   39   System shall provide the ability to place STAT orders without signatures
        (to be obtained later)
   40   System supports nursing documentation for "read back" of verbal orders
   41   System supports signing of verbal orders
   42   System supports links to external websites and networked documents
        during order entry if necessary
   43   System should support the processes for restricting orders by provider type

   44   System supports customizable indication of pending/active orders
   45   System shall provide the ability to flag pending orders; for example, orders
        that need co-signatures and supports multiple signatures (cosign or
        cosigns)
   46   System shall provide the ability to automatically route and/or interface
        orders to appropriate departments/units
   47   System supports the ability to automatically communicate a cancelled
        order to the appropriate department (internal or external)
   48   System shall provide the ability to alert nursing, etc. if there is an order
        requiring immediate review
   49   System shall provide the ability for nursing to acknowledge the order
        requiring immediate review was viewed
   50   System supports the ability to notify caregiver of overdue tasks; notification
        should be customizable
   51   System shall provide the ability to support staff changes with notifications
Appendix F: 2. Hospital Based Core Clinicals
   52   System supports ability to create orders based on patient workload/acuity
        management
   53   System shall provide the ability to auto-page consult to notify of a referral
   54   System supports secure messaging (on-demand or automatic) via e-mail,
        pager, PDA to providers regarding orders requiring signatures, order
        status, results, etc.
   55   System supports ability to customize clinical messaging / alerts by provider

   56   System shall provide the ability to send secure messages regarding orders
        and results to other providers who initially review and triage
   57   System shall provide the ability to notify physicians when patients are
        admitted and discharged
   58   System shall provide the ability to notify attending physician when new
        orders have been entered STAT
   59   System shall provide the ability to activate a consult and have its new
        status displayed in the main record
   60   System shall provide the ability to display orders after discharge if patient
        is readmitted, based on Hospital criteria
   61   System supports ability to discontinue all inpatient orders at discharge in
        one step
   62   System shall provide the ability to enter recurring orders on an outpatient
        basis, for orders relating to areas such as chemotherapy.
   63   System supports complete audit trail of orders, reviews, results routing, etc.

   64   System shall provide the ability to automatically track order status with
        different levels of tracking; ability for orders to "fall off" the list when
        completed
   65   System shall provide the ability to report overdue orders (not yet
        completed)
   66   System shall provide the ability to customize view of orders & results
   67    System supports the options to continue or cancel orders (in whole or
        part) as patients transfers to another level of care
   68   System shall provide a flag for confidential or VIP orders. Provide user
        ability to initiate confidentiality.
   69   System shall provide the ability to view orders by MD Name and or MD
        code
   70   System shall provide customizable order sorts; for example alphanumeric,
        department, frequently ordered, for single orders and order sets
Appendix F: 2. Hospital Based Core Clinicals
   71   System shall provide the ability to report on orders usage (including order
        sets, drug protocols, etc) by provider and in aggregate including reports on
        which order priority physicians most often use, and which physician uses a
        given priority most often, and other user-defined criteria
   72   System supports the generation of worklists by all provider types and
        sortable by user-defined criteria (unit, treating MD, date, services to
        deliver, therapy schedules, etc.)
   73   System supports auto-printing orders in single and multiple locations for
        those areas not integrated with the CIS.
   74   System shall have the ability to track Advanced Beneficiary Notices
        (ABNs) for labs/procedures
   75   System shall provide the ability for orders entered by a physician to
        automatically generate that physician's charges upon completion of
        documentation, administration, etc.
   76   System supports all accreditation and regulatory requirements. System
        should support the ability to link documentation to orders (for areas such
        as pain scales and med administration) as well as contain CDS to guide
        clinicians to evidence based care. This data must be easily retrievable for
        reporting purposes

   77   System shall provide the ability to document/review providers and those
        special procedures/drugs they are credentialed to perform/order.
   78   System shall provide the ability to enter an add-on lab order (when
        specimen is in lab).
   79   System shall provide the ability to view specimen collection information
        online while statusing a specimen as collected (full test name; specimen
        type; container type; volume; any special instructions).
   80   Active orders can be viewed as a group and appropriate orders can be
        selected and copied upon transfer to a new level of care
   81   System has the capability to save orders as written without activating them
        until ordered to do so
   82   System support duplicate checking to evaluate identical active, held or
        unsigned orders
   83   System shall provide the ability to view patient's transfusion history
        Order Sets/Protocol
   84   System shall provide the ability of system to recommend treatment
        protocols (and orders) based on selection of chief complaint or diagnosis
        with the ability to override the recommendations
   85   System shall provide the ability to update recommended treatment
        protocols and order sets given a change of diagnosis
Appendix F: 2. Hospital Based Core Clinicals
   86    System shall provide the ability to build order sets and documentation
         screens for procedures
   87    System shall provide the ability to customize order sets by dept, provider,
         population etc. (i.e., remove one item from a set)
   88    System shall provide ability to easily cut and paste from multiple order sets

   89    System shall provide the ability for restriction of order sets based on role,
         i.e. attending, resident, etc
   90    System supports the creation and maintenance of diagnosis and provider-
         specific order sets that can be modified by a user during order entry


   91    System shall provide the ability to enter multi-department orders in one
         order set (i.e.; lab, radiology, pharmacy, etc) which would be automatically
         communicated/routed to appropriate locations
   92    System supports the ability to release orders at the item level when
         entered as an order set.
   93    System shall support "blank" ranges w/in an order set, for example, "ABG
         if Sa02< __ "
   94    System supports various types of order sets - i.e., mandatory (orders
         cannot be removed from set) or recommended (orders can be removed
         from set)
   95    System supports the ability to view ordering protocols online
   96    System shall provide the ability for two or more order sets to be merged
         and duplicate orders be automatically flagged
   97    System shall provide the ability for a clinical guideline to initiate an order
         set and vice versa
   98    System shall provide the ability to expedite the order process for MDs who
         frequently use a given order set
   99    System shall provide the ability for medication doses to be auto-calculated
         in individual orders and order sets based on patients age and weight


         Results Reporting
   100   System shall provide the ability to route results to ordering providers and/or
         other providers for review and show status of review (who and when) via a
         printer, fax, e-mail or a provider worklist based upon result
   101   System supports the display of new results within flowsheets that also
         include previous and other test results
   102   System shall have ability to suggest an update to the diagnosis during
         ordering based on recent results
Appendix F: 2. Hospital Based Core Clinicals
   103   System supports the printing of results
   104   System supports ability to redirect results if sent to wrong provider
   105   System supports role and user-based verification and validation
   106   System shall provide for specific order data to be automatically pulled into
         the result report based upon exam type (e.g., patient history, reason for
         exam, order date & time, CPT number, procedure, etc)
   107   System supports automatic out-of-office notification in provider absence
         and supports automatic forwarding of results to covering provider
   108   System supports the ability to store pointers and launch images from
         results view
   109   System supports auto-escalation if results have not been viewed for a pre-
         defined time parameter
   110   System provides ability for clinician to acknowledge results and document
         interventions.
   111   System will calculate length of time to acknowledgement for critical lab
         values (JCAHO requirement)
   112   System provides the ability to electronically compare value by trending and
         graphing
   113   System provides the ability to show inpatient to outpatient test results
   114   System shall provide the ability for data from a disparate lab system to be
         captured for results and integrated into clinical decision support (e.g.,
         medication management decision making).
         Medication Management
   115   System supports ability to document allergies, reactions and severity from
         codified lists and view audit trail of documentation
   116   System shall provide the ability to support bar code medication
         administration (BCMA).
   117   System shall support use of RFID and/or proximity checking for medication
         administration as an alternative. Please describe your system's
         capabilities.
   118   System shall accommodate bar coding bracelet size for pediatric patients
   119   System provides prompts/alerts for clinical documentation associated with
         medication administration
   120   System shall provide the ability to link with payer formularies and provide
         alternatives to medication if needed
         Medication Selection View and Sorts
   121   System shall provide the capability to do an alpha search for look-up (e.g.
         typing the letters PEN would drop down a list of medications including
         penicillin, penvk, etc)
Appendix F: 2. Hospital Based Core Clinicals
   122   System supports a single medication list across patient care continuum of
         home, ambulatory, ER, inpatient, etc. Please describe how you propose to
         address this with disparate systems for these various venues.
   123   A patient‟s single medication list supports drill down to provider, date &
         time, and reason for each entry
   124   System supports ability to have multiple sorts from medication selection
         catalog; For example, alpha sort, generic vs. brand name sort, drug cost,
         therapeutic index, therapeutic category, most frequently used medication,
         by route within generic, top dollar
   125   System supports ability to restrict formulary items based on credentials or
         investigator status (e.g., chemotherapy restricted to oncologist)
         Medication Order Entry
   126   System shall provide the ability to set multiple frequencies for medication
         administration (e.g., BID and Now)
   127   System shall provide the ability to specify orders in milligram per kilogram
         of body weight or body surface area using actual, ideal or adjusted weight
         with ability to round the final dose
   128   System supports multiple methods of medication order entry; For example
         generic name, brand name, mnemonics, order sets, phonetic names,
         protocols, "per pharmacy"
   129   System shall provide the ability for medications to follow the patient when
         he/she transfers units
   130   System shall provide the ability to adjust, reorder, auto-cancel medications
         upon transfer
   131   System shall provide the ability to notify provider(s) of transfer and the
         need to review orders
   132   System shall provide the ability for unit staff to see if pharmacist has
         reviewed recent order
   133   System displays formulary status and therapeutic substitution prompts
         upon order entry.
   134   System supports customizable, flagged "required" fields that must be filled
         by user during order entry (unique to medication at dispensing level)


   135   System supports ability to embed order sets within an order set (e.g.,
         embed heparin protocol within unstable angina orders)
   136   System supports ability to free text enter medications not on medication list
         and to document rationale (i.e., "non-formulary"), with the capability to
         make the documentation required
Appendix F: 2. Hospital Based Core Clinicals
   137   System supports ability to enter complex orders such as insulin sliding
         scale, steroid taper, PCA or epidural; heparin protocol, extemporaneously
         compounded products, simultaneous administration of products by use of
         templates, customized medication screens, etc
   138   System allows a mandatory pharmacist verification function following non-
         pharmacist entry to transfer an order from non-verified to active/verified
         status
   139   System allows a mandatory pharmacist verification for modifications to
         active orders
   140   System shall provide the ability to update standing order sets or predefined
         orders with formulary changes in one step (approved autosubs, dosing
         changes, etc)
   141   System supports real-time detection and reporting of potential and
         confirmed medication errors, ADEs, patient incidents, with automatic
         information flow to quality systems this includes surveillance and ADE
         checking including pediatric focus for alerts and CDS
   142   System shall provide the ability to have two or more co-signatures and
         alert the provider(s) and pharmacist when 2+ signatures are needed
   143   System shall provide the ability to track start and stop times for
         medications with automatic reminders when the timeframe has expired and
         prompts for the MD to order renewal
   144   System shall provide the ability to communicate and document double
         verification of medications (during the ordering or administration process)
   145   System shall provide the ability to order and document medication range
         orders (i.e., MSO4 2 – 5 mg), per JCAHO rules
   146   System shall provide the ability to capture license and DEA number during
         the ordering process as appropriate
         Medication Review Screens
   147   System supports ability to view and print user-defined medication lists
         such as current medications; administration history of specific medications;
         cumulative doses; start/stop dates, etc
   148   System supports ability to show a summary list of all previous medications
         (now discontinued) for a patient, with ability to drill-down into details of
         usage
   149   System supports ability to graph lab results and medication dose history
         (e.g., INRs vs. warfarin doses)
         Discharge Medications / Medication Reconciliation
Appendix F: 2. Hospital Based Core Clinicals
   150   System shall provide the ability to perform medication reconciliation -
         record the meds/treatments a patient was on at admission vs. at
         discharge, populate a transfer/discharge form, and mark the differences.
   151   System supports medication reconciliation upon discharge, and all levels
         of patient transfer in accordance with JCAHO regulatory requirements


   152   System shall provide the ability to alert physician to unusual
         medications/routes of administration (i.e., compounded Rx) that may be
         difficult for a patient at home
   153   System shall provide the ability of discharge order templates to have
         different fields than inpatient templates for the same medications (i.e.,
         number of tablets dispensed, # of refills)
   154   System supports ability to populate discharge medication information to
         various forms including patient transfer forms, printed prescriptions,
         education materials
   155   System shall support e-prescribing to support routing of prescriptions for
         take home medications electronically to the patient's pharmacy of choice.
   156   System shall provide the ability to alert PCP of discharge medications
   157   System shall provide the ability to document medication teaching was
         provided to patient
         eMAR
   158   System supports alerts for new med orders upon entering the eMAR
   159   System supports Pharmacy verified orders to populate the eMAR
   160   System allows RN to view all medication orders while awaiting verification
         by pharmacy
   161   System provides ability to obtain and document on the eMAR stat and
         emergent medications without pharmacist verification, provided positive ID
         for ordering MDs and nurse(s) administering the drugs
   162   System shall be flexible to set RN order verification parameters by site,
         unit and order type
   163   System supports ability to flag appropriate clinician(s) if medication
         administration schedule is not met
   164   System supports user-defined required fields for the eMAR
   165   System shall provide the ability to document (including justification) for
         doses not administered and ensure charges are not incurred
   166   System shall provide the ability to report on reasons doses not administered
   167   System provides hyperlink from the eMAR to medication information
         database and other reference sites
Appendix F: 2. Hospital Based Core Clinicals
   168   System supports ability to meet requirements for printed copies of eMAR
         to use during downtimes
   169   System supports display of complex administration schedules
   170   System supports ability to charge on administration, dispensing, or daily
   171   System shall provide the ability to change times on the pharmacy schedule
         and eMAR and include comment for justification.
   172   System shall provide the ability to document past administration times on
         the eMAR
   173   System has flexible window around drug administration time to
         accommodate patient schedule
   174   System shall provide the option to print drug-specific administration
         instructions directly on the eMAR.
   175   System provides easy access to drug information, including protocols or
         guidelines from the eMAR
   176   System shall provide the ability to co-sign for each dose given and track
         when it has occurred
   177   System supports customizable, user-defined eMAR views, such as single-
         page meds list and administration schedule by patient or chronology, time-
         based reviews (i.e., 7 days, 1 day)
   178   System supports customizable, user-defined eMAR charting
   179   System shall have distinct areas on eMAR for Scheduled meds, PRN
         meds, One-time or STAT doses, Chemotherapy, IV narcotic drip section,
         and IV fluids and drips


   180   System shall link eMAR to bar coding process
   181    System shall have the ability to link medication administration to
         appropriate assessments
         Additional Requirements
   182   System supports bi-directional interface to IV pumps, and verification of
         drip rates and drug via bar code. Specify IV pumps you have interfaced
         with and maximum (if any) that can be interfaced to your system.


   183   System supports user defined reporting of alerts and medication status
   184   System supports "shift reports" of medications administered over past X
         hours
   185   System supports med order interface to drug dispensing machine
   186   System provides physician access the eMAR for clinical monitoring
Appendix F: 2. Hospital Based Core Clinicals
   187        System supports prompts to alert nursing to re-assess pain after pain
              medication administration including linking to clinical documentation flow
              sheets
   188        System shall provide the ability to support changes in Peak and Trough lab
              draw times if an antibiotic administration time changes
   189        System shall provide the ability for documentation of change in patient
              status to alert to change route of delivery of a medication
   190        System shall provide the ability to document blood product processing and
              administration
   191        System shall provide the ability for the system to require two RN's to verify
              weight based meds with documentation of calculation
   192        System shall provide the ability to generate a list of all patients receiving a specific medication
   193        System shall automatically upload/download patient immunization data to/from immunization registry
              Clinical Decision Support
   194        System includes an embedded Clinical Decision Support (CDS) application
              that will support alerts based on:
         a        Order conflicts
         b        Order duplications
         c        Clinical indication (i.e. treatment protocol)
         d        Available substitutions
         e        IV to PO conversions
          f       Lab values
         g        Patient age/weight/other demographic information
         h        Allergies
          i       Drug-drug interaction
          j       Drug-food interaction
         k        Drug-Disease interaction
          l       Pediatric alerts
         m        Wrong drug/wrong dose/wrong route/ wrong patient, etc.
         n        Medical necessity
         o        No authorization
         p        Clinical standards of care
         q        Min/max alerts for 24 hour period
   195        CDS system shall be delivered with a starter set of rules that may be
              modified by SMMC to meet patient care standards and requirements
   196        Rules may be designated with effective dates or sunset dates
   197        System shall support multiple levels of alerts, and may be designated to
              not allow override, stop the process, etc. without department head
              authorization, etc.
Appendix F: 2. Hospital Based Core Clinicals
   198   Rules and alerts can be developed and assigned based upon roles (i.e.
         resident vs. attending physicians).
   199   System communicates alerts to all relevant parties and supports other
         media for communication (e.g., pager, on-screen display, cell phone, etc.).


   200   System provides alert regarding medications that are near discontinuation.

   201   System shall support the ability to view summary results and drill-down to
         user-defined detail
   202   System shall provide the ability for the user to define age and weight
         norms, and pediatric abnormal lab values
   203   System shall provide ability to define age / weigh norms and abnormal
         values for bariatric patients.
   204   System shall support multiple preliminary, interim, and final versions of
         ancillary results, (i.e., 24, 36 and 48 hour interim microbiology results)
   205   System shall provide the ability to view Evidence Based Medicine
         protocols based on Evidence Based Medicine content, e.g., Zynx,
         Lippincott, etc.
   206   System shall provide the ability to trigger an alert to the clinician when an
         evidenced based/preferred/core measure order is deselected in an order
         set.
   207   System shall support on screen reminders specific to patient, diagnosis,
         medication or other clinical interaction
   208   System shall support flowsheets based on guidelines of care
   209   System shall support Disease Management trend analysis
   210   System shall provide the ability to assign specific documentation fields
         based on roles
   211   System shall support flexible statistics graphing capabilities including
         control charts
   212   System shall provide the ability to measure and report on outcomes,
         quality and appropriateness
   213   System supports alerts in response to a specific action or lack of an action
         such as placing an order or not documenting required clinical information
         within a specified timeframe
   214   System shall provide the ability to store alert responses and repeat the
         alert if one of the parameters changes, i.e., MD overrides alert for drug-lab
         interaction b/c the patient has a history of chronic renal failure, resend the
         alert if the patient‟s lab value changes
Appendix F: 2. Hospital Based Core Clinicals
   215   System shall provide the ability for an individual clinician to set the patient-
         specific value where they want to see an alert (i.e., notify me if serum
         creatinine is above 6)
   216   System shall provide the ability for clinicians to view the criteria for a
         clinical rule and/or view the reference source materials for that rule
   217   System shall support a display of relevant data when entering an order,
         i.e., display most recent Digoxin level, heart rate, serum potassium and
         heart rhythm/ectopy when ordering Digoxin
   218   System shall support the ordering of services (nutrition consult, PT
         consult) and provide recommended interventions based on patient
         parameters, i.e., nutrition assessment score, Rehab screens
   219   System shall support Employee/patient safety tasks based on
         documentation, i.e. initiate fall/risk protocol according to criteria based on
         fall/risk score
   220   System shall provide a missing clinical documentation report at the patient
         care unit level
   221   System shall support the display of relevant cost data and suggest more
         cost-effective therapy at the time of clinician orders
   222   System shall support the matching of patient specific values against pre-
         established criteria and provide a message if the patient does not meet the
         criteria, (i.e., InterQual, ICU admission criteria, hospital discharge criteria)


   223   System shall support routing a message or report to the appropriate
         person based on the “priority” of the event
   224   System shall provide the ability to calculate patient severity or risk score
         based on patient data, i.e., APACHE score and acuity levels for nurse
         staffing. Please indicate how the acuity is calculated by your CIS.


   225   System shall provide the ability to capture and report response to alerts
         (incl. frequency of alert, overrides (by provider), when therapy was altered
         b/c of the alert, etc.)
   226   System shall provide the ability to do analyses/reports of variances from
         pathways/protocols, and outcomes
   227   System shall support the collection of JCAHO Core Measures data as a by-
         product of the care delivery/documentation process
   228   System shall support easy to build, customizable rules and alerts per role,
         specialty and site (location) or by combined variables
   229   System shall provide the ability for physicians to customize the alerts they
         receive
Appendix F: 2. Hospital Based Core Clinicals
   230   System shall provide the ability for clinicians to bypass/"snooze" alerts and
         specify a timeframe when they would like the alert to re-trigger
   231   System shall provide the ability to review the type of alert - Regulatory or
         department
   232   System shall provide the ability to display medical evidence associated
         with an alert and when the evidence was last updated.
         Clinical Documentation
   233   System shall provide the ability for physician documentation of a patient's
         history and physical exam to be auto-populated with data that's already in
         the system. System shall distinguish which data is auto-populated.This
         includes medications, allergies, and past medical history.
   234   System shall provide the ability to copy and paste information from one
         part of the record to another. System shall provide a mechanism for which
         the clinician can verify the accuracy of the information prior to entry.


   235   System shall support conditional branching and collection of additional
         data elements using logic defined in assessment forms.
   236   System shall provide the ability to arrange standard preventive/ follow-up
         care based on user defined criteria (on age, gender, diagnosis, history)
         and display data during clinician charting session or recall (generate letter)
         for provider review and modification.
   237   System should allow the recording of different expressions of age, such as
         gestational age, chronological age, and corrected age
   238   System shall support documentation and maintenance of customizable,
         problem lists using NANDA and other association problem list standards
         and etiologies used as reference including national standards bodies for
         the incorporation of coded data (SNOMED, LOINC, etc.)
   239   System shall provide for a continuous problem list summary (Inpatient &
         Outpatient) that contains ICD-9/ICD-10 (future) codes; with the capability of
         a historical view.
   240   System shall provide the ability to drill down into problem list to review
         details for each problem (service, time, reason, last changes)
   241   System shall support providers with continuous, active patient summary
         list with drill down to details, including provider, staff, last patient contact.


   242   System shall provide a patient admission profile (based on organizational-
         defined needs i.e. including mandatory fields) online and hardcopy
         including: admission/ registration data, diagnosis, signs, allergies, nursing
         history, text comments, type of admission, etc.
Appendix F: 2. Hospital Based Core Clinicals
   243   System shall provide the ability for a physician to continue home med list,
         and list reason(s) why a medication should not be continued.
   244   System shall provide the ability to communicate medication list to patient,
         PCP, and ambulatory clinics upon discharge
   245   System shall support interdisciplinary documentation with customizable,
         discipline-specific assessments, care paths, and treatment sheets and
         forms (accommodates multiple types of documentation including but not
         limited to structured flow sheets, free-text flow sheets)
   246   System shall support tracking of variances to pathways and prompts for
         clinicians to document rationale for the variance (or update the pathway)
   247   System shall support documentation entry outside of the pathway which
         can append to the pathway
   248   System shall provide the ability to merge two pathways so that duplicate/
         conflicting orders are identified and resolved in the pathway
   249   System shall provide the ability to prompt staff re: incomplete
         documentation
            - audible "you need to chart"
            - flags in chart showing note as "in progress"
   250   System shall supports standard (i.e. SOAP and others models) and
         customized progress note/ H&P/ documentation templates by Physician,
         Nurse, OT/PT/ST, Medical Abstractor, Research Topic, etc with the ability
         to integrate with other documentation
   251   System shall provide the ability for clinicians to copy forward previous
         progress note data into current exam portion of clinician documentation
   252   System shall provide the ability to retrieve images and include in
         documentation w/annotation
   253   System shall support calculations such as Intake and Output,
         hemodynamic calculations, infant fluids as well as custom calculations as
         defined by the organization (i.e. decreasing IV rates based on fluid intake)


   254   System shall support customizable viewing of I & 0 current and cumulative
         totals with breakdown of content (i.e. Output = & urine, & NG tube, etc.)


   255   System shall support charting against the problems list. System shall
         provide the ability to link and create a note from patient's problem list.
   256   System shall provide user-defined help screens with custom content
         related to the form the user is accessing
   257   System shall provide the ability to restrict confidential data (i.e. HIV status)
         to certain roles
Appendix F: 2. Hospital Based Core Clinicals
   258   System shall provide a flag for confidential result entries (e.g., HIV status
         and alcohol treatment record - Social concern alerts - HX of violence,
         mental, health issues) with ability to provide audit trails of access.


   259   System shall provide the ability to display progress notes by user-defined
         sorts.
   260   System shall support easy editing/ correcting with time/ date and signature
         stamp for data entered with the ability to see original data.
   261   System shall support the integration of outpatient and inpatient defined
         data elements.
   262   System shall support a defined data element set that crosses encounters/
         episodes of care.
   263   System shall support customized discharge documentation by patient
         condition, diagnosis or orders. Templates should capture predefined
         events (clinical documentation) and timestamps .
   264   System shall provide the ability to customize screen layout and flow by
         specialty or service area, by provider, etc.
   265   System shall provide the ability for documentation to support coding.
   266   System shall provide the ability to integrate information from dictation and
         speech recognition
   267   System shall provide the ability to view a free form report from transcription
         and dictation.
   268   System shall provide the ability to assign several healthcare provider
         relationships (i.e., resident, attending, admitting MD, consulting, PNP,
         FNP, NNP etc.) and set up alerts based on role
   269   System shall support multiple views of patient information based upon
         access requirements.
   270   System shall support co-signatures and multiple signatures with the ability
         to "route" notes to the co-signer via worklist or other modality and alert the
         cosigner of the signature request.
   271   System shall provide the ability for cosigner to edit note prior to sign-off
   272   System shall support linkage between the eMAR and discharge summary
         and provide the ability of the eMAR to send discharge medications to
         discharge summary.
   273   System shall provide the ability to automate discharge summary
         distribution, including to providers outside of the core institution.
   274   System shall provide the ability to customize the discharge summary
   275   System shall support current biomedical device interfaces (cardiac
         monitors, fetal monitor, tele, IABP, IV pumps and vents)
Appendix F: 2. Hospital Based Core Clinicals
   276     System shall support the capturing and displaying results from third-party
           instruments (e.g. EKG, Holter, Treadmill)
   277     System shall support capturing and displaying data from point-of-care
           devices, e.g., glucometers.
   278     System shall provide the ability to verify information that is downloaded
           from biomedical devices / instruments
   279     System shall provide the ability to select patient flags and alerts that
           should be communicated to the various ancillary departments, including
           isolation alerts on orders; e.g., flag patients with special needs (interpreter,
           wheelchair)
   280     System shall provide the ability to denote/communicate actual patient
           weight was not obtained. Clinician should be alerted to obtain actual
           weight when patient condition warrants.
   281     System shall provide rules to indicate required documentation (e.g. a pre-
           op visit requires the completion of an H&P)
   282     System shall supports prompts for pre-requisite testing completion prior to
           interventions
   283     System shall have the ability to calculate BMI
   284     Plans of Care
           System shall support he development of interdisciplinary, standardized
         a care plans/clinicsl paths e.g. asthma, CHF, etc.
           System shall flag if a plan of care has not been initiated within a user-
         b specified period of time
           Sytem shall identify variances from clinical pathways/plans of care and
         c allow for reporting of the variances
           System shall support plan modification, version tracking and reference
         d lookup
           System shall provide the ability to generate a plan of care from
         e assessment data
           System shall provide the ability to track patient progress against plan of
         f care outcomes and interventions
           System shall enable orders, which are entered after the plan of care has
         g been assigned, to be incorporated into the plan of care
           Support plans of care that span across the enterprise continuum as well as
         h visit/episode specific plans
           Pediatric Growth Charts
   285     The system shall provide the ability to utilize pediatric growth charts,
           including editing, graphical trending and statistical analysis.
Appendix F: 2. Hospital Based Core Clinicals
   286   Growth charts should contain the following data elements: age, gender,
         height and weight, head circumference, and the date and clinic location
         that measurement was taken.
   287   System shall have the ability to create and/or customize new charts as
         needed for specific syndrome-centric multiple growth charts; specific
         diseases and chronic conditions (e.g., Turner or Downs Syndrome);
         expectation based on parental height, etc.
   288   Growth charts shall contain automatic indications of surgical and drug
         interventions that could be pertinent to the patient‟s growth patterns (e.g.,
         scoliosis surgery; growth hormone administration)
   289   System shall provide the ability to add specific criteria for percentile and
         growth calculations (e.g., upper/lower segment ratios, arm span, etc.)
   290   System shall have the ability to maintain up to 21 years of growth history to
         include time, date, and service location
   291   System shall have the ability to calculate Z scores for all points and in
         particular for those < 5 or > 99 percentiles
   292   System shall have the ability to customize view/print routines (e.g., ability
         to convert inches to centimeters & vice versa)
   293   System‟s growth chart shall have flexible annotation tools so that clinicians
         can easily add plot point annotations that may be pertinent to the patient‟s
         growth pattern
   294   System shall have a turn-around time for growth chart availability that is
         less than 1 second (no more than 10 seconds) from the point of data entry
         (as opposed to data gathered), to include previous growth history, if
         applicable.
   295   System shall have an auto-alert at point of data entry in growth chart when
         a value falls outside a defined range.
   296   System shall provide the ability for the user to correct their own invalid
         growth chart entries and/or flag previous entries when they are assumed to
         be incorrect.
   297   System shall provide the ability to add field requirements to growth chart
         that relate to “conditions at data collection” (e.g., patient was fully clothed,
         patient in diaper only, etc.)
         Workflow
   298   System supports new result indicators for lab, text reports, orders. Real
         time; audible or visual display - multiple alarms based on severity of results


   299   System supports worklists that are time oriented and can be viewed by
         multiple clinicians. Ability to print work list for designated time frame.
Appendix F: 2. Hospital Based Core Clinicals
   300   System supports the ability to auto-populate worklists from orders, care
         plans, user defined/entered data and can be sorted / viewed by various
         parameters.
   301   System supports ability to transfer worklists to other clinicians and "sign-
         out" user, so no tasks populate task list while user is "signed-out".
   302   System shall provide the ability to document transfer/ hand-offs between
         residents/ staff at end of shift, including creating "to do" lists
   303   System shall support the ability to easily change patient's attending
         physician. Unresulted orders, alerts, and messaging should be
         automatically transferred to new physician
   304   System shall provide the ability to review, respond, and route messages
         (multiple message types, including lab results notification, staff messages,
         phone calls, addendum notification, order notification, transcription)


   305   System supports the ability to delegate message viewing to other staff
         (e.g. when a provider is out of office);
         Clinical: Review
   306   System shall support drill-down capabilities from summary views by
         encounter, diagnosis, medication, order, imaging, and laboratory history
   307   System shall support graphical and numeric flow-sheeting of laboratory
         and other data including normal values
   308   System shall provide the drill-down history of clinical episodes, including
         allergies and drug sensitivities
   309   System shall support customizable clinical summary by specialty or site
   310   System shall support preliminary reads and the ability to archive
         preliminary reads upon final read.
         Charging
   311   System supports the ability to charge against documentation. System
         should be able to distinguish between procedures handled by different
         clinicians whether a charge should be dropped or not, i.e. if RT performs a
         treatment a charge is generated, if a nurse performs the same treatment a
         charge is not generated. Similarly a charge can be generated if procedure
         performed by a licensed physician for certain insurances, but not if
         performed by an unlicensed one.

   312   System supports the ability to send orders and diagnoses entered during
         chart documentation to a revenue cycle system to generate a bill.
   313   System has capability to capture professional charges for inpatient
         physicians, e.g., rounding visits.
Appendix F: 2. Hospital Based Core Clinicals
   314   System shall provide the ability to monitor billing justification and advise on
         compliance.
         System has ability to alert the attending when notes are needed as part of
         supervision of the residents.
   315   System supports clinical documentation driving E&M charging levels.
         Additional Requirements
   316   System shall provide the ability to list all providers for each patient and
         indicate what types of patient information they should receive (i.e.,
         research, patient care, etc.)
   317   System shall provide the ability to recognize a blank PCP field and route a
         message to a report and/or inbox for eligibility screening and PCP
         assignment
   318   System shall support printing of visit summaries and/ or discharge
         instructions/education materials for patients at various reading levels and
         in multiple languages; Spanish is required. (List all languages your system
         supports).
   319   System shall provide the ability to support specialized formats for patient-
         specific information required for teaching rounds or other educational
         activities
   320   System supports the development of customized rounding/census reports,
         e.g., by specialty, by provider, etc.
   321   System shall provide the ability to merge educational material/ teaching
         instructions from multiple areas into one document for the patient
   322   System shall have the ability for patient education material to include
         diagrams and pictures
   323   System shall provide the ability to document that teaching material and
         instructions were given to the patient (who, what, when)
   324   System shall provide the ability to print a summary of events from
         caregiver for the patient, guardian, or other providers
   325   System shall provide the ability to view discharge items based on
         insurance coverage (i.e. transportation, discharge medications, etc)
   326   System shall provide the ability for documentation (i.e. H&P) to be started
         in one area ( the ER) and finished on the unit, possibly by a different
         provider.
   327   System shall provide the ability to document patient change of service and
         have orders and/or pathways continue upon transfer
   328   System shall provide the ability to display/ print anticipated discharge date
         based on conditions and/or link from Case Management system. Please
         describe your features.
Appendix F: 2. Hospital Based Core Clinicals
   329   System shall provide the ability for discipline specific care plans - i.e. rehab
         plan - or the ability for standard care plan to incorporate the specifics


   330   System shall support the use of inter-disciplinary care plans.
   331   System supports documentation/ retrieval of patient consent forms,
         Advanced Directives, Power of Attorney, Conservator, Flu shot
         preferences, etc.
   332   System shall provide for the recording of assent for treatment from an
         underage adolescent or child as well as consent for treatment from an
         older adolescent or parent
   333   System shall provide the ability to support electronic signature by patients
         for consent, etc.
   334   System supports patient-entered data (i.e. from patient portal or from
         assessment forms in-house to be scanned or input via OCR)
   335   System supports the ability for patient/parent sign-off of home medication
         and allergy information in support of JCAHO reconciliation requirements.
   336   System supports spell check of free text, including a medical dictionary
   337   System shall provide the ability to schedule follow-up appointments with
         clinic prior to inpatient discharge
   338   System supports re-use of prior note/ documentation with ability to update
         with current values
   339   System shall provide the ability to review and supervise student/resident
         work
   340   System shall provide the ability to print or send d/c instructions
         electronically to patient, home care, or transitional care site
   341   System shall provide the ability to document and calculate therapy-specific
         data, such as total active motion, averages, median
   342   System shall provide the ability to include streaming video into
         documentation
   343   System shall provide the ability to support generating letters for regulatory
         and reporting purposes (i.e. to Dept of Health for child in protective custody)


   344   System supports ability to correct errors in notes /re-assign documentation
         done on incorrect patient
   345   System shall provide the ability to support special alerts at discharge (i.e.
         underage mother requires social worker or relative to sign discharge)
Appendix F: 2. Hospital Based Core Clinicals
         System provides the ability to start a note and save it without letting it be
         live in the system until finalized by the provider (e.g. an intern starts a
         discharge summary two days prior to the discharge, but finalizes it when
         the patient actually gets discharged)
   346   System shall provide the ability to record start/ end time of treatment
         sessions
         Bed Management
   342   Please describe in detail bed management functionality in your CIS when
         integrated to a a foreign ADT system. Include processes such as:
         transfer/dischafge, bed board display capability, patient location tracking,
         acuity display and usage, etc. Please be specific in your response.
      APPENDIX F: 3. CRITICAL CARE
                                                                                                                       Vendor Response:
NO.                                       FUNCTIONAL REQUIREMENT                                                            Availability     Est. Delivery   Additional
                                                                                                                           (3, 2, 1, or 0)        Date         Cost
      CRITICAL CARE
      Data Capture
      System shall provide the ability for data to be automatically captured from intravenous devices and
 1    stored and available to auto populate user defined reports.
      System shall provide the ability for data to be automatically captured from bedside monitoring devices,
 2    e.g., interface with IV pumps
      System shall provide the ability for standard "vent check" data to be automatically captured from
 3    ventilators. Please describe this process.
      System shall provide the ability to enter notes and/or comments annotated on a chart at a relevant
 4    location for every data item. The ability to recall those notes by clicking on the annotation in the chart.
 5    System shall provide the ability to establish “pick lists” from a table
      System shall provide the ability to search long pick-lists by typing in the first few letters or a wild string
 6    already provided
      System shall provide the ability to configure system for 24 hour totals from 7a.m. to 7p.m. (or other user
 7    defined time frame)
 8    System shall provide the ability to calculate fluid totals based on mg/kg/day for 24 hour totals.
      Vital Signs
      System provides user configurable time intervals for capturing vital signs from the monitors (i.e. every 15
 9    seconds, every hour etc); Ability to verify or accept prior to chart entry.
10    System shall provide the ability to manage artifacts from the patient monitors
      System shall provide the ability to validate vital signs coming from the monitor prior to commitment to the
11    chart
      System supports on-line charting of vital signs and display of vital signs via manual (handheld) input or
12    wireless devices
13    System shall provide the ability by unit to define defaults on on-line vital sign screens
14    System supports automatic on-line display of vital signs in text or tabular format
15    System supports automatic display of vital signs in graphical format
      System provides graph plots of charted vital sign data (e.g. heart rate, arterial systolic and diastolic
16    pressures) directly above the corresponding tabular data
      System shall provide the ability to capture and present greater than five graphs per patient from various
17    bedside monitoring devices
      System shall provide the ability for Vital sign graphs to illustrate multiple overlapping vital signs (specify
18    maximum to a graph)

      Key
      3 = Currently Available Installed
      2 = Available with Modifications
      1 = Under Development
      0 = Not Available                                                                                  3. Critical Care                                                 Page 25
      APPENDIX F: 3. CRITICAL CARE
                                                                                                                          Vendor Response:
NO.                                       FUNCTIONAL REQUIREMENT                                                               Availability     Est. Delivery   Additional
                                                                                                                              (3, 2, 1, or 0)        Date         Cost
19    System shall provide the ability to change the range of the baseline scale, by user
      System shall provide the ability to specify whether parameters are plotted as points or connected points
20

21    System shall provide the ability to graph/plot vital signs against weight, growth curves, etc.
      System shall provide the ability for user to add or delete vital sign parameters for individual patients to on-
22    line flow sheet from a menu or pick list
      System provides ability to configure specific vital sign entries to require validation with electronic
23    signatures before storing data permanently
      System provides automatic range checking of vital sign values as they are input or electronically
24    acquired. Warn user of values that are out of range
      System provides a method to distinguish un-verified vital sign data on a screen (e.g. with different color,
25    italics or highlighted)
      System provides ability for user to override or edit data gathered from bedside monitors to correct errors
26    and provide warnings (results outside "normal" range)
      System shall provide the ability to maintain vital sign data on-line for an individual unit, as opposed to
27    across the board for a defined period of time.
      Intake and Output
28    System supports automated tracking of fluid intake and output (I &O) in an automated flowsheet
      System shall provide the ability to display fluid intake and output flowsheet values on-line in a tabular and
29    graphic format
      System shall provide the ability for user to add or delete fluid I&O items for individual patients to on-line
30    flowsheet via free text entry, menu or pick list
      System shall provide the ability to flag fluid I&O items on screen as D/discontinued when discontinued
31    and have the cursor skip over when charting these volumes
32    System supports tracking of I&O items by volume or occurrence
      System shall provide the ability to define by patient or unit specific master list of fluid I&O items for on-line
33    flowsheet
      System shall provide the ability for unit to define times for nursing shift periods for I&O tracking and
34    totaling purposes
      System shall provide the ability by unit to define day begin and end times for I&O tracking and totaling
35    purposes to from 7a.m. to 7p.m.
36    System shall provide the ability for continuous shift and 24 hour running totals for all fluid I&O records
37    System supports automated tracking and display of fluid I&O subtotals by type (e.g. urine, gastric)

      Key
      3 = Currently Available Installed
      2 = Available with Modifications
      1 = Under Development
      0 = Not Available                                                                                    3. Critical Care                                                  Page 26
      APPENDIX F: 3. CRITICAL CARE
                                                                                                                      Vendor Response:
NO.                                       FUNCTIONAL REQUIREMENT                                                           Availability     Est. Delivery   Additional
                                                                                                                          (3, 2, 1, or 0)        Date         Cost
38    System shall provide the ability to track blood product completion time
      System supports the definition of default volume, concentration, amount, dose and rate for each IV drug
39

      System automatically recalculates IV parameters (e.g. concentration, dosage) when one is changed for a
40    specific patient
41    System provides electronic interface to an IV pump for automatic charting of IV rate values
42    System shall allow the user to define and track any fluid output as needed for a patient
      System shall provide a continuous output record with separate columns for different output records (e.g.
43    urine, chest tube)
44    System shall provide ability to display graphs of hourly output
      System shall provide the calculation of fluid balances in cc/kg/hr and be able to be calculated for 12 and
45    for 24 hours
      System supports having numerical values displayed in a flowsheet format with the ability to scroll up and
46    down
      Hemodynamics
      System shall provide the ability to view greater than 5 pressures and/or calculations at a time and to
47    configure what pressures can be viewed by unit.
48    System shall provide the ability to track and report hemodynamic calculations
      System shall interface wth tissue oximetry monitors (using near infrared spectroscopy (NIRS)) Please list
49    units with which you interface.
      System shall interface with non-invasive cardiac output monitoring devices. Please units with which you
50    interface.
      System shall provide the ability to synchronize and print 2 chosen channels for cardiac, resp. cycle
51    identification, e.g. PCWP interpretation, documentation
      Ventilation
      System shall provide the ability to customize high frequency ventilation (oscillatory) flowsheets (i.e.,
52    customize the defaults) including settings for HFOV.
      System shall provide the ability to access ventilator orders within 10 seconds of sign on (if greater than 10
53    seconds, please specify how long)
      Additional Requirements
54    System shall provide tools to track inpatient mortality




      Key
      3 = Currently Available Installed
      2 = Available with Modifications
      1 = Under Development
      0 = Not Available                                                                                 3. Critical Care                                                 Page 27
      APPENDIX F: 3. CRITICAL CARE
                                                                                                                      Vendor Response:
NO.                                       FUNCTIONAL REQUIREMENT                                                           Availability     Est. Delivery   Additional
                                                                                                                          (3, 2, 1, or 0)        Date         Cost
      System shall provide the ability for ICU documentation templates to be pre-populated with ED, OR, or
55    historically collected data (e.g. meds, allergies, etc). Describe how you would handle this assuming the
      ED and OR systems are disparate from your CIS/ICU module.
56    System shall provide the ability to show contact information for close relatives and guardians
      Additional Clinical Documentation: Critical Care
      Clinician Charting / Automated Billing / Procedure Logs
      System shall provide the ability for critical care physician documentation of a patient's daily progress and
      physical exam to be auto-populated with data that's already in the system. System shall distinguish for
      the clinician which data in the daily progress note is auto-populated, and provide the option to amend and
55
      delete autopopulated data. System shall calcuate automatically and autopopulate daily progress note with
      hospital day, ICU day and post op day as appropriate

      Documention to be autopopulated in daily progress note include current vital signs (including a user
      selected 24 hour period's high and low of blood pressure, heart rate, respiratory rate, mean arterial
      pressure, central venous pressure, oxygen saturation, temperature both maximum and current, and
      24hour intake and output including hemodialysis), problem list from previous day's note with options to
      update changes, current respiratory and ventilator settings ( including respiratory rate, tidal volume, fi02,
      mode of ventilation, PIP and PEEP, and use of high frequency ventilator or intermittent percussive
      ventilation), diagnostic imaging reports and images from the previous 24 hours, echocardiogram
56
      summaries, ECG reports, cardiac cath summaries, laboratory tests from the previous 24 hours including
      latest updated microbiology results from urine, sputum, wound and blood cultures including antibiotic
      sensitivities, current scheduled and prn medications including antibiotics with their cummulative duration
      of therapy, intravenous drip medications including current administration rates, enteral or intravenous
      feeds with 24 hour totals and current rates.


      System shall provide the ability for clinician documentation to be signed by single or multiple treating
      physicians, including intern, resident, fellow and attending physicians. Attending physicians automatically
      prompted for billing for patient care services at time of signature, including total time of critical care
57    managment, with level of billing determined automatically from documentation, ICD-9 codes pre-
      populated from previous days billing with option to amend or delete codes, and billing report generated
      and sent automatically to hospital billing system.




      Key
      3 = Currently Available Installed
      2 = Available with Modifications
      1 = Under Development
      0 = Not Available                                                                                  3. Critical Care                                                Page 28
      APPENDIX F: 3. CRITICAL CARE
                                                                                                                   Vendor Response:
NO.                                       FUNCTIONAL REQUIREMENT                                                        Availability     Est. Delivery   Additional
                                                                                                                       (3, 2, 1, or 0)        Date         Cost
      System shall provide the ability for the clinician to document procedures in preconstructed templates for
      common procedures. Customizable report templates will include consent, indication, conscious sedation,
58    time out, procedure and complications. System shall prompt physicians for all current state mandated
      components for central line insertion reporting, and automatically forward a customizable report to
      infection control in a format that can be sent to the state reporting office.

      The system shall provide a mechanism for retrevial of data and construction of quality assurance reports
      of each critical care physician (including interns, residents, fellows and attendings) invasive procedures
      including monthly and annual summary reports of the total procedures by type, indications, complications
      and unit where performed. In addition, the system will have the capability to generate aggregate reports
59    of invasive procedure by service or location. For resident physicians, an additional report to be sent to
      program directors procedure log documenting date, procedure, and supervisor as well as a cummulative
      summary for their residency to date. System will then prompt supervising physician to confirm and
      evaluate residents performance of the procedure.

      Multidisciplinary Team Charting / Report generation
      System shall provide the ability for non-physician members of the multidisciplinary ICU care team such as
      pharmacy, speech therapy, physical therapy, occupational therapy, social services, palliative care,
      chaplain services, case management, respiratory therapy, and nutrition to generate documentation for
      individual patients. Inaddition, multidisciplinary team member shall be able to generate summary reports
60
      of all patients by unit or service, with user selected components from all data available in the system,
      including name, location, diagnosis, laboratory, demographics / religion and medication data for
      screening of patients.

      Automatic Generation of Transport Orders for Interhospital Transfers
      System will support automatic generation of current orders for interhospital transfer, with automatic
      population of diagnosis, allergies, ventilator, intravenous drips, and scheduled medications, with options
61    to amend and delete autopopulated orders, and print a hard copy for the transport team and receiving
      hospital. Automatic medication reconcilliation report generated for medical record.
      Restraint and Seclusion Orders and Documentation
      Automatic prompts to clinician to document need for restraints and renew orders prior to expiration
      of24hour for medical restraints, and 4 hours for behavioral restraints. Single page unit based or medical
62    service based screen showing all restraint orders, and time of expiration for each clinician's service,
      allowing them to renew all restraint orders for all their patients from one screen.
      Decubitus Ulcer and Skin Documentation


      Key
      3 = Currently Available Installed
      2 = Available with Modifications
      1 = Under Development
      0 = Not Available                                                                               3. Critical Care                                                Page 29
      APPENDIX F: 3. CRITICAL CARE
                                                                                                                        Vendor Response:
NO.                                       FUNCTIONAL REQUIREMENT                                                             Availability     Est. Delivery   Additional
                                                                                                                            (3, 2, 1, or 0)        Date         Cost
      Automatic prompts for physician to cosign any entry by nursing of either skin examination or photograph
      of skin breakdown. Ability to add free text or selected comments to entry. A pictorial decubitus staging
63    guide to help the clinician decide on stage of the breakdown followed by a prompt to enter stage.
      Automatic reporting to wound consult service

      Additional Requirements: Critical Care
      Remote viewing of ICU flowsheets
      Remote viewing of ICU flowsheets from physician offices, call rooms, tablets, and home PCs. Ability to
      track entire user selected patient panels / critical care units from one screen. System ability to set up
64    target goals and notifications for user definable variables, including blood pressure parameters, urine
      output, ICP, heart rate, oxygen saturation for entire panels of patients , with the capability to drill down to
      individual patient flowsheets.

      Septic Shock Management
      System ability to set up time based targets to achieve hemodynamic endpoints for septic shock
65    management
      Quality Management
      System will have the be able to maintain a user definable and sortable database of all patients admitted
66    to the ICUs which autopopulates with diagnosis,treating physcians, length of stay, length of stay on
      ventialtor, mortality, severity of illness score and complications.
      Emergency Orders
      System will allow clinicians to place retroactive orders for emergent situations such as drugs given for
67    codes and intubations,
      Patient Discharge Instructions and Prescriptions
      For patients discharged directly from the ICUs, system will provide modifiable templates for general
68    instructions, followup appointments, required medications, as well as specific instructions relavent to their
      disease (chest pain, DKA/ diabetes, etc)
      Discharge prescriptions electronically transferred to off-site pharmacies, including a searchable list of
69    local pharmacies.
      Attending Of Record
      The attending of record for each medical team will be verified on the first day of each rotation by the
      system and updated for all pateints on that service. The frequency of the automatic update will be user
70    selectable, and customizable for each service. When incorrect, the attending of record will be easily
      modifiable by the clinician to the appropriate attending.
      Physcian OnCall

      Key
      3 = Currently Available Installed
      2 = Available with Modifications
      1 = Under Development
      0 = Not Available                                                                                  3. Critical Care                                                  Page 30
      APPENDIX F: 3. CRITICAL CARE
                                                                                                                     Vendor Response:
NO.                                       FUNCTIONAL REQUIREMENT                                                          Availability     Est. Delivery   Additional
                                                                                                                         (3, 2, 1, or 0)        Date         Cost
      The housestaff and physician staff oncall schedule will be linked to the patient record, with a single tab
71    revealing names and pagers of the primary and backup physcians to be called, and updated
      automatically 24 hours around the clock
      Automatated Data Sign in and Display
      Upon physician entry into the patients room, the system will recognize the physician by RFI or security
      token, and automatically display on a bedside monitor, all patients currently available datafrom the last
      24 hours including vital signs graphs, intake and output,, morning labs, current medications / drips, as
72    well as status on ordered/completed tests, with links to microbiology results and radiology images. The
      format of the display will be a physician specific customizable template applied to all patients under care
      of each physician.

      Neurocritical Care Monitoring
      System will track neurologic function, including Glascow coma scale, sedation scale, pain scale, ICP
      measurements and cerebral oxygen saturation, calculate cerebral perfusion pressure, and have the
73    ability to display all data relevant to neurocritical care patient care, including medications for sedation,
      and relevant imaging results on a separate dedicated flowsheet




      Key
      3 = Currently Available Installed
      2 = Available with Modifications
      1 = Under Development
      0 = Not Available                                                                                3. Critical Care                                                 Page 31
APPENDIX F: 3. CRITICAL CARE

                       Comments




Key
3 = Currently Available Installed
2 = Available with Modifications
1 = Under Development
0 = Not Available                   3. Critical Care   Page 32
APPENDIX F: 3. CRITICAL CARE

                       Comments




Key
3 = Currently Available Installed
2 = Available with Modifications
1 = Under Development
0 = Not Available                   3. Critical Care   Page 33
APPENDIX F: 3. CRITICAL CARE

                       Comments




Key
3 = Currently Available Installed
2 = Available with Modifications
1 = Under Development
0 = Not Available                   3. Critical Care   Page 34
APPENDIX F: 3. CRITICAL CARE

                       Comments




Key
3 = Currently Available Installed
2 = Available with Modifications
1 = Under Development
0 = Not Available                   3. Critical Care   Page 35
APPENDIX F: 3. CRITICAL CARE

                       Comments




Key
3 = Currently Available Installed
2 = Available with Modifications
1 = Under Development
0 = Not Available                   3. Critical Care   Page 36
APPENDIX F: 3. CRITICAL CARE

                       Comments




Key
3 = Currently Available Installed
2 = Available with Modifications
1 = Under Development
0 = Not Available                   3. Critical Care   Page 37
APPENDIX F: 3. CRITICAL CARE

                       Comments




Key
3 = Currently Available Installed
2 = Available with Modifications
1 = Under Development
0 = Not Available                   3. Critical Care   Page 38
     APPENDIX F: 4. ENTERPRISE DOCUMENT MANAGEMENT
                                                                                                                               Vendor
                                                                                                                            Response:
No                                          FUNCTIONAL REQUIREMENT
                                                                                                                             Availability     Est. Delivery   Additional
                                                                                                                            (3, 2, 1, or 0)        Date         Cost
     ENTERPRISE DOCUMENT MANAGEMENT (EDMS)
     Structure, set up and maintenance
     System shall provide centralized management of the structure and set up by the System Administrator or other
1
     authorized personnel
2    System shall track the development and maintenance of all configurations over time.
     System shall allow system administrator to make global amendments to the structure of the folders, documents,
3    in a single process
     System shall provide system administrator ability to create, move, reconfigure or rename folders or document
4    structure and will maintain an history/audit trail for transactions, including original location and option to enter
     reason for action.
     System will allow the re-assignment of records form one folder to another by a system administrator, retaining
5    transaction history and access levels.
     System will allow abiilty perform system maintenance, data integrity processes without downtime or disruption to
6    users. Describe process for system maintenance and data integrity.
     System shall allow system administrator or designee to move a folder or group of folders and their attached
7    records without disruption to any existing structural links, securty, access level and transaction history.
     Document Capture
     System shall support archiving of previous converted paper records (i.e., with MPI backload) and ongoing
8    capture of ad hoc paper components integrated with the clinical information system (CIS)/electronic health
     record (EHR):

           Archival of pre-go-live converted paper records (i.e., back scanning and/or back loading of electronically-
9          generated documents) (i.e. in conjunction with MPI backload) (e.g. lab, radiology, pathology reports, etc.)),
           if desired, including the history of a folders origination and audit history for all documents, and structural
           links for all folders.
           Capture, during the migration from paper-based records to a new CIS/EHR, of entire medical records via
10
           combination of scanning and electronic (COLD) feeds.
           Import from or export/link to other systems for document transfer including activity sets,metadata and
11
           transaction history
12         Notification to system administrator when controls linked to import, exports/link are updated.

13
           Capture/integration of ad hoc paper documents with the clinical information system/electronic health record

     Key
     3 = Currently Available Installed
     2 = Available with Modifications
     1 = Under Development
     0 = Not Available                                                                              4. Ent Document Mgmt                                                   Page 39
     APPENDIX F: 4. ENTERPRISE DOCUMENT MANAGEMENT
                                                                                                                              Vendor
                                                                                                                           Response:
No                                         FUNCTIONAL REQUIREMENT
                                                                                                                            Availability     Est. Delivery   Additional
                                                                                                                           (3, 2, 1, or 0)        Date         Cost
           Capture/store all ad hoc documents/objects in their native format and replicates the documents from the
14
           source/generating system
          Capture documents from diverse sources including fax, copier-scan-transaction, digital upload, multimedia
15
          and email maintaining an audit history of transaction, source location, date, time and metadata if applicable.
16   System shall support concurrent scanning/indexing by an unlimited number of individuals
17   System shall support capture of electronic messaging, such as email including attachments.
     System shall support individual and batch scanning with batch reconciliation tools to identify misfeeds or double
18
     scans Decribe process
     System shall support single and multiple page COLD-fed documents - COLD includes any text-based
19   documents, imported images, digital objects (e.g. PDF) (including those that may be created via a virtual printer
     from the originating system). Decribe how SMMC can create these imports at the local level.
     System shall automatically generate a sequential numeric reference for document batch which will be searchable
20
     and remain a part of the document history.
     System shall support error reporting on COLD document processing including queue for interface errors with
21
     automated/ customizable notification to system admninistrator or designee

22
     System shall support ability to import multiple image formats, e.g., JPG, TIF, PDF, RTIF, multimedia formats etc.
     System shall support ability to receive ASC X12N 271/HIPAA 5010 equivalent eligibility inquiry response
23   transactions and store as images. Indicate if clearinghouses are used for this processing and if so, which do you
     partner with?


24   System shall support ability to receive ASC X12N 837/HIPAA 5010 equivalent transactions for claim forms and
     store as images. Indicate if clearinghouses are used for this processing and if so, which do you partner with?


25   System shall support ability to receive ASC X12N 835/HIPAA 5010 equivalent transactions for EOBs and store
     as images. Indicate if clearinghouses are used for this processing and if so, which do you partner with?
     System shall support scanning of paper-based EOBs/RAs and capture of appropriate patient-specific images at
26
     the account level (single patient's information in each image).
27        Image includes header and footer of original page along with EOB/RA information for that patient only
           Pointer to the entire EOB/RA is available so that a user viewing the EOB/RA image for a patient can click
28
           and be routed to the entire EOB/RA


     Key
     3 = Currently Available Installed
     2 = Available with Modifications
     1 = Under Development
     0 = Not Available                                                                          4. Ent Document Mgmt                                                      Page 40
     APPENDIX F: 4. ENTERPRISE DOCUMENT MANAGEMENT
                                                                                                                             Vendor
                                                                                                                          Response:
No                                         FUNCTIONAL REQUIREMENT
                                                                                                                           Availability     Est. Delivery   Additional
                                                                                                                          (3, 2, 1, or 0)        Date         Cost
           Document capture process also captures key data elements such as denial codes and payments so that
29
           payments may be automatically posted as if this were an 835 transaction
30         Captured data elements may be used to kick off workflow processes, e.g. denial management
31         Captured data elements may be exported to spreadsheet and/or database applications
     System accepts, stores and allows viewing of DICOM images for radiology images done externally and not
32
     electronically available via interface/viewer to PACS system.
     System has lock-out features if multiple people are trying to scan images to a single patient's chart
33
     simultaneously. Please describe.
34   System shall support multiple scanner settings (various sizes, orientation, contrast, double-sided, color etc.)
     System shall support original sizes ranging from insurance cards, to driver‟s licenses, personal checks, to larger
35
     and irregular items
     System shall support scanning of color and black and white photographs , e.g. wound, patient ID, intraoperative,
36
     etc.
37   System shall support the automatic manipulation of a skewed document without re-scanning
     System shall support the automatic adjustment of contrast/brightness of complex images (e.g. photo IDs,
38
     insurance cards) or images for originals on colored paper
     System shall support copying of images to multiple folders vs. rescanning into each folder maintaining history
39
     and audit trail for each page.
     System shall support automatic deletion of blank pages based on user defined criteria at the folder, document
40
     and document type level
41   List type of scanners and specfic manufacturers that can be utilized with this application.
     Storage/ DESTRUCTIONS
     System shall support automatic archiving to long-term storage based on user-defined criteria. System will
42
     prevent automatic archiving of documents that are not complete or have identified deficiencies.
43   System shall support logical and physical purging of images based on user defined retention schedules
     System informs user of current location of documents (on-line, near-line, offline). Describe how the system
44
     informs users

45
     System shall support multiple storage media e.g. SAN, NAS, DVD, etc. Describe preferred storage schema.
     System provides rules criteria for controlled destruction of records legally authorized for disposal based on
46
     system administrator defined criteria from one day to indefinite periods. Describe function.


     Key
     3 = Currently Available Installed
     2 = Available with Modifications
     1 = Under Development
     0 = Not Available                                                                           4. Ent Document Mgmt                                                    Page 41
     APPENDIX F: 4. ENTERPRISE DOCUMENT MANAGEMENT
                                                                                                                               Vendor
                                                                                                                            Response:
No                                         FUNCTIONAL REQUIREMENT
                                                                                                                             Availability     Est. Delivery   Additional
                                                                                                                            (3, 2, 1, or 0)        Date         Cost
     System shall allow customizable creation of definitions and rules for destruction based on specific document
47
     types, dates, folders, etc.
     System shall be able to maintain a history of all changes to the destruction rules, including date of change and
48
     reason for change
     System shall restrict the ability to create, edit, and delete destruction rules for documents to the system
49
     administrator
50   System records all destruction actions in an audit trail
51   System will allow a destruction freeze to be placed on the record, folder, document to prevent destruction.
52   System will allow purging and destruction of records after validation from system administrator or desginee


53   System will support an automated destruction process consisting of identification of records, folders, documents
     for which the retention period has elapsed and notification of system administrator prior to destruction completion.
     Record Structure
54   System shall support multiple levels of file-folder hierarchy, including 3 steps below document type
     System shall support unlimited number of records that can be allocated to a folder or captured within the entire
55
     system. If not unlimited, maximum number of records
     System shall support both patient-centric and non-patient centric indexing schemas, e.g. MRN, account number,
56
     employee ID, date, vendor, custody identifiers, etc.
57   System shall support MRN-level patrient level (global) documents (e.g. advance directives, patient ID, etc.)

     System shall allow system administrator or designeed to close a folder, ensuring that no new records can be
58   added to the folder, recording the closing date and the reason. A closed folder will maintain viewing and
     retrieval functionality.
     System will prevent the destruction or deletion of folders, records and associated transaction history, including
59
     metadata at all times- except for the purposes of destruction.
     System must restrict the ability to amend the content of a record to highest level of system administrator and
60
     provide strict controls over the amendment process. Describe process.

     System shall allow users to annotate the document/folders with alerts, notes. Describe how alerts can function
61
     and the ability to customize the content.

62
     System shall support physical/logical separation of patient-centric information from non-patient-centric information



     Key
     3 = Currently Available Installed
     2 = Available with Modifications
     1 = Under Development
     0 = Not Available                                                                          4. Ent Document Mgmt                                                       Page 42
     APPENDIX F: 4. ENTERPRISE DOCUMENT MANAGEMENT
                                                                                                                            Vendor
                                                                                                                         Response:
No                                         FUNCTIONAL REQUIREMENT
                                                                                                                          Availability     Est. Delivery   Additional
                                                                                                                         (3, 2, 1, or 0)        Date         Cost
     System shall support physical/logical separation of different instances of non-patient-centric information, i.e.
63
     employee information from accounts payable type information
     Document Indexing
     System shall support indexing of documents via both system-defined and customized user-defined options.
64
     Please describe.
65   System shall support „drag/drop‟ for indexing to the patient‟s account/record, maintaining transaction history.
66   System shall support auto-indexing via bar-coding and/or OCR to expedite the indexing process
     System shall support indexing a digital record/image/document to more than one folder, maintaining a document
67
     history to assure if changes are made to one document the same change could occur to the other.
68   System shall warn a user attempting to index a document that is already indexed to a folder.
     System shall support ability to easily move an individual document from one account/record to another and/or
     from one document type to another (to address misdirected documents files) including transaction history
69
     including metadata
     System shall support the use of a fax-server or copier/scan technology or email to receive images with a queuing
70
     mechanism to support workflow for indexing faxed "document images". Describe
     Faxed-in/remote transmitted (from copier) images are processed from the same application instance of
71
     document capture queues as are scanned and COLD documents with retained transaction history.
     Additional Document Capture Functionality
     System shall support automatic assignment of signature deficiencies to clinicians for electronic (COLD)
72
     documents (e.g. transcribed reports)
     System can support and/or interface to document deficiency tracking and monitoring system. Describe
73
     deficiency system or systems supported by this EDMS
74   System provides remote access capabilities for electronic signature and document deficiency completion.
75   System provides electronic signature capability that includes dual authentication. Describe

     System shall support manual assignment of physician deficiencies during the indexing process, i.e., particularly
76   for "loose" reports and electronically received/ faxed-in orders (integration of document indexing and deficiency
     analysis functions) with ability to annotate or provide notes to a physician.
     System provides a method to delete/strip all images from a patient account if that patient is a 'no show' at the
77   facility, i.e., patient is registered and populates the document imaging system but then does not show for
     appointment. Please explain process.
     System shall allow email of physician deficiency notifications that are customizable to occur when deficiency is
78
     assigned or on a pre-defined schedule based on user defined critiera.

     Key
     3 = Currently Available Installed
     2 = Available with Modifications
     1 = Under Development
     0 = Not Available                                                                            4. Ent Document Mgmt                                                  Page 43
     APPENDIX F: 4. ENTERPRISE DOCUMENT MANAGEMENT
                                                                                                                                   Vendor
                                                                                                                                Response:
No                                          FUNCTIONAL REQUIREMENT
                                                                                                                                 Availability     Est. Delivery   Additional
                                                                                                                                (3, 2, 1, or 0)        Date         Cost
     System shall be able to recognize additional providers identified on a document and email or notify them based
79
     on customizable criteria.
     System shall be able to track physician deficiencies for purposes of reporting, suspension and customizable
80
     record management functions.
     System shall have a customizable provider data table that will support deficiency tracking, status that can be
81
     easily integrated with systemwide provider profiles.
     System shall support cutting/pasting information from one text-based document to another. Please describe.
82
     System will reference the source document when paste completed and maintain a transaction history.
     EXTRACTION AND REDACTION
     The system will allow the creation of an exact replicate of a record, whereby sensitive information is hidden from
     view in the extract, while the originating record remains intact. The replicated document will retain history in
83
     metadata data, a transaction history which includes date, time, creator and reason for extract. Please describe
     process and sample document with extraction process demonstated.
     The system will create a navigable link between an extract (replicated document) and the original record from
84   which is was taken. Such a link should preserve the relationship between the extract and the source record
     wihtout compromising the access and security controls applicable to the record.
     Integration
     System provides the ability for all images (scanned or interfaced/COLD) to be organized and available within the
85   patient's medical (i.e., in clinical information system/EHR) and/or financial record (i.e., in patient financial system)
     without the need to 'launch' to a separate document management system (EDMS).
86   Structure of chart configuration, i.e., location of data/tabs, etc. shall be configurable by client.
     System shall support receipt and storage in the patient's record, and display of text-based outside reports (e.g.
87
     transcription from physician practices)
     System shall support integration of document capture within the admitting/registration process via prompts for
88   documents throughout the registration process and/or ability to batch scan once the registration has been
     completed
89        If photo ID exists for the selected MRN, image displays without searching for it
90        Includes the ability to recognize bar codes during the batch scanning process


91         Generates both on-line and printable consent forms with support for patient/representative digital signature
           pads, wireless eSignature (specify if a separate application), or other applicable technology. Describe.

     Key
     3 = Currently Available Installed
     2 = Available with Modifications
     1 = Under Development
     0 = Not Available                                                                              4. Ent Document Mgmt                                                       Page 44
      APPENDIX F: 4. ENTERPRISE DOCUMENT MANAGEMENT
                                                                                                                                   Vendor
                                                                                                                                Response:
No                                           FUNCTIONAL REQUIREMENT
                                                                                                                                 Availability     Est. Delivery   Additional
                                                                                                                                (3, 2, 1, or 0)        Date         Cost
               Electronically generated/signed documents are able to be sent directly to the EDMS without printing,
92
               maintaining transaction history and metadata.
93             System supports digital clipboards, tablets, signature pads and remote signature options.
              eForms application provides fillable forms; completed fillable forms are sent directly to the EDMS without
94
              printing, maintaining the transaction history and metadata.
95          Document capture may be either wireless or wired Decribe wireless process
            Documents created electronically can be e-signed. The e-signatrure will include a date/time stamp and
96
            dual authentication signature. Describe electronic signature options and abilty to customize.
            Documents created though e-form or electronically and not printed will allow routing to diffferent providers
97
            for review and e-signature. Specify if this requires a separate application.


98    System shall support integration with module that supports record deficiency tracking and electronic record
      completion, e.g.,. clinicians do not have to log in to additional application for record completion Please describe
      System provides reporting functionality, including ad hoc reports, to track physician deficiencies, send automated
99
      notification of pending records for completion. Provide Samples
      System shall support integration with module that supports release of information If release of information is
100
      not integrated, describe release of information modules that support an interface and describe functionality.

      Release of information module allows batch printing for selected documents to paper, CD, electronic file.
101
      Specify all out put media.
      Release of information requests can be managed from within the ROI application while accessing documents
      stored in the EDMS. Describe the Release of Information application and workflow.
      Release of information module includes automatic logging, flexible document selection process, and batch
102
      printing. Describe the release of information workflow
103   System supports integration with a clinical data coding and abstracting module. Please describe
104   System can support computer assisted coding. Please describe.
      System shall support routing of all results and physician data/reports received (whether discrete data or images)
105   to the provider's "inbox" in the CIS for review/signoff or copies automatically sent to offsite physicians if indicated
      via email, electronically within the system, or fax.
      Searching/Viewing




      Key
      3 = Currently Available Installed
      2 = Available with Modifications
      1 = Under Development
      0 = Not Available                                                                             4. Ent Document Mgmt                                                       Page 45
      APPENDIX F: 4. ENTERPRISE DOCUMENT MANAGEMENT
                                                                                                                             Vendor
                                                                                                                          Response:
No                                         FUNCTIONAL REQUIREMENT
                                                                                                                           Availability     Est. Delivery   Additional
                                                                                                                          (3, 2, 1, or 0)        Date         Cost
      System provides the ability to search for folders based on user-defined criteria e.g. MRN, account number,
106   employee ID, date of birth, patient name, employee name, vendor, etc. with appropriate security to view the type
      of information requested, maintaining an audit trail and transaction history for all criteria.
107   System provides the ability to search for documents based on keywords
108   System provides the ability for users to view multiple document images on one screen – “thumbnails”
109   System shall support clear viewing capabilities (zoom, rotate, contrast, new window/tab, etc.)
      System provides a user customizable ability to chronologically display documents of a single type (e.g. consents,
110
      EKGs, authorizations) for review and comparison purposes across a patient's visits
      System provides the ability for each user to define the way they view the documents to which they have been
111
      granted access
      System provides ability to view patient level documents from within any of the account numbers associated with
112
      this patient
113   System shall support use of electronic "sticky" notes
114   System shall support use of "highlighters"
115   System allows annotation on images, with appropriate security
116   System provides ability to bookmark at folder (e.g. account), document, and page level
      Output
      System has ability to output (e.g. print, fax, encrypted e-mail, download to CD or other media) entire medical
117   and/or financial record and/or components, with the appropriate security, and regardless of the origin (scanned,
      imported or COLD) and will maintain a transaction history for output.
118   System has the ability for the user to select images for output at all levels (patient, document, page)
      System has the ability to export images to other systems (assumes the other system can receive it), maintaining
119
      all tranasction history and metadata. Decribe formats for transmittal
      System has the ability to place a visual customizable cue on each output page (i.e. "printed (or faxed, etc.)…"
120
      with date/time/user noted

121
      Header, footer verbiage is customizable by trained SMMC personnel with the option for vendor support if needed
      System provides the ability to produce an audit history from within the EDMS application - date/time printed/e-
122
      mailed/faxed/copied to CD/DVD, status, fax number sent to/from, user ID, etc.
123   System will encrypt documents before electronic transfer.
124   System will be able to restrict the option for copy and paste. Describe
125   System will be able to restrict the option for printing based on user access level, patient or document type.

      Key
      3 = Currently Available Installed
      2 = Available with Modifications
      1 = Under Development
      0 = Not Available                                                                         4. Ent Document Mgmt                                                     Page 46
      APPENDIX F: 4. ENTERPRISE DOCUMENT MANAGEMENT
                                                                                                                            Vendor
                                                                                                                         Response:
No                                            FUNCTIONAL REQUIREMENT
                                                                                                                          Availability     Est. Delivery   Additional
                                                                                                                         (3, 2, 1, or 0)        Date         Cost
126   System prints/outputs documents with customizable patient identifiers/transaction information on all pages
      Fax/ TRANSACTIONS
127   System provides the ability to customize a cover sheet for each fax/ transactions
128   System provides a daily fax/ transaction log.
      Workflow Capabilities
      Describe the workflow capabilities and abiltiy to create work queues for routing documents for analysis, coding,
129   release of information, quality review, peer review, etc.
130   System shall support the ability to begin the workflow process based on:
            Capture of a specific document type (e.g. Release of Information request, refund request, Release of Body
131
            form, etc.)
            ADT (i.e., based on pre-registration, registration, admission, transfer, discharge, other HL7 transaction
132
            types)
            Customizable assignment of a task to a user or group of users based on document type, physician,
133
            financial class, length of stay, type of service, etc. Describe process for assignment.
134         Database search
135         Typing in/capturing a list of folders

136   Describe how the system shall support the ability to create workflow processes/queues for specific purposes:

 a         Deficiency analysis
 b         Coding
 c         QA of registration process (i.e., missing required documents)
 d         Release of Information
 e         Denial management
 f           Based on the denial codes received in electronic remittances
 g         Peer Review
 h         External, regulatory reviewers
137   System provides the ability to easily reassign work from one user or group of users to another. Describe
      System shall support the ability for workflow expansion (customizing and adding) without degradation to system
138
      performance.
      System shall support the customization of workflows by trained SMMC staff with the option to come to vendor for
139
      support if needed


      Key
      3 = Currently Available Installed
      2 = Available with Modifications
      1 = Under Development
      0 = Not Available                                                                           4. Ent Document Mgmt                                                  Page 47
      APPENDIX F: 4. ENTERPRISE DOCUMENT MANAGEMENT
                                                                                                                             Vendor
                                                                                                                          Response:
No                                          FUNCTIONAL REQUIREMENT
                                                                                                                           Availability     Est. Delivery   Additional
                                                                                                                          (3, 2, 1, or 0)        Date         Cost
      System shall support the ability for supervisors to monitor workflow in real-time and manipulate queues
140
      accordingly in real time
      System provides options to email, fax, print documents based on criteria for physician record completion, release
141
      of information, denial management and document review criteria.
142   System will provide encryption for documents transmitted electronically

143   Workflow software comes packaged with library of starter work objects that enable workflows to be built quickly

144   Workflow capabilities support the reprioritization of work items in queues
      Workflow-Related Reporting
      System provides flexible customizable report design - Describe process and specify any special report writers or
145
      vendor assistance required. Provide samples of reports.
      System provides the ability for supervisors to view the status of all work queues in report format Provide sample
146
      reports.
      System provides customizable productivity reporting for each queue showing tasks completed, pended, skipped,
147
      deleted, etc. by user by a range of dates Provide sample reports
      Access & Security
      System provides role-based access to documents, patient information based on authenticaion mechanism (user
148
      name/ password/biometrics) Describe authentication options.
149   System must restrict the folder design, structure, amendments and changes to a system administrator.
150   System must restrict setup and changes to user profile, access and security set up to a system administrator.
151   System must restrict central user table including access/rights/inactive status to a system administrator
      System shall allow the configuration of access and security controls to support unique and flexible controls
152
      based on folder, document, including rules related to the use (ie. print, view, bookmark, etc).
153   System shall allow layers of access set up at the record, folder and user level.
154   System shall allow the customizable user access groups, with customizable access based on the group.
155   System shall support one user being assigned to mulitple groups to support access and security.
      System must ensure that records and folders inherit the access and security controls based on the higher levels
156
      of the record hierarchy under which they are created.
157   System will support integrated network log-in (single sign in)
      System provides the ability to limit access to records of patients with certain patient types or services (e.g.
158
      behavioral health, infectious diseases, etc.)


      Key
      3 = Currently Available Installed
      2 = Available with Modifications
      1 = Under Development
      0 = Not Available                                                                            4. Ent Document Mgmt                                                  Page 48
      APPENDIX F: 4. ENTERPRISE DOCUMENT MANAGEMENT
                                                                                                                                   Vendor
                                                                                                                                Response:
No                                           FUNCTIONAL REQUIREMENT
                                                                                                                                 Availability     Est. Delivery   Additional
                                                                                                                                (3, 2, 1, or 0)        Date         Cost
      System provides the ability to grant access to users to view a specific set of documents and to output that same
159
      set of documents or only a subset of those documents
160   System provides the ability to limit printing/faxing/e-mail/electronic transmittal based on user access
161   System provides the ability to link access of employees of physician practices to their physician(s)
      System provides the ability to provide access to only a specific "set" of folders - e.g. patient medical/financial
162   information, employee health information, HR information, accounts payable information, physician credentialing
      information, etc. Decribe process
      System allows locking of an entire folder (i.e., at MRN level) or a set of folders (i.e. certain accounts under an
163
      MRN) for security so that only authorized users may access this information Describe this function.
      System provides user customized alerts at the patient, episode and document level. Describe the type of alerts
164   and if alerts woulld identify amendments or restricted documents. Describe if a transaction history is
      maintained for all alerts
      System will provide version control to identify mutliple versions of a single document through its life cycle to meet
165
      e-discovery mandates at the time of implementation, maintaining a transaction history for each version.
      System can support "break the glass" options to allow a user to obtain access to specific patient information in
166
      an emergent situation. Describe the technology and how this may occur.

167
      System allows locking of a single document for security so that only authorized users may access this document
      Audit Trail
      System maintains an audit trail of every page of every document that is accessed/processed (e.g. viewed,
168
      printed, faxed, e-mailed, scanned, indexed, signed, annotated, etc.)
169   System can support customizable access monitors that requires user to identify purpose of access.
      System provides automatic alerts for access activity to a specific document type, patient name or customized
170
      criteria to decrease the concerns with breech or unauthorized activity.

171
      System provides option to link employees to specific records based on customizable criteria to prevent access.

      The System must be able to maintain a complete record of all events performed within the system as an audit
      trail, including: list of users; failed login; failed attempts to view a record; attempts to access restricted records,
172   attempts to access system functions associated with system administrator; action carried out; document
      accessed; date and time of the event; printing; emailing; faxing, etc. Please list all unique data elements that
      can be captured on the audit trail.
173   System must ensure that the audit trail can be easily exported without affecting the original audit trail.

      Key
      3 = Currently Available Installed
      2 = Available with Modifications
      1 = Under Development
      0 = Not Available                                                                             4. Ent Document Mgmt                                                       Page 49
      APPENDIX F: 4. ENTERPRISE DOCUMENT MANAGEMENT
                                                                                                                                    Vendor
                                                                                                                                 Response:
No                                           FUNCTIONAL REQUIREMENT
                                                                                                                                  Availability     Est. Delivery   Additional
                                                                                                                                 (3, 2, 1, or 0)        Date         Cost
174   System must protect the audit trails against modification by any user, including system administrator.

      System must be able to automatically record information in the audit trail about the following events: Creation of
      a new user or group; data time of all transactions; changes to access and security controls affecting a record,
175   folder or user; relocation of records to another folder, indentification of both origin and destination; relocation of a
      folder to a different part of the record identification of both origin and destination; date and time of a change to
      metadata; placing or removal of a freeze, sequester or access level.
      System provides flexible reporting on all audit data without impacting system performance while reports/inquiries
176
      are running
      Reporting
      System provides robust productivity management reporting (e.g. scanning, indexing, documents deleted, etc.) by
177
      user by a range of dates, document types, activity. Describe and provide samples.
      System provides robust reporting of all document transactions during a documents lifecycle - from input, output
178
      through destruction.
      System provides a report that shows all documents quality reviewed by a user and transaction history for all user
179
      transactions, including deletions.
       System provides a report that shows the number of documents a user indexed and to which accounts these
180
      documents were indexed
      System provides management reports to identify documents waiting to be indexed, quality checked or that have
181
      not been permanently assigned to a document folder
182   System provides error reporting for COLD errors, scanning errors, etc.
      System provides customizable reporting for all data elements available based on the document capture, storage
183
      process.
184   System provides reporting for accounting of disclosures
      Retracted State Items
185   System allows for removal of a record or note from view and provides space for a reason for removal.
186   System allows for access to a retracted record or note to selected staff.




      Key
      3 = Currently Available Installed
      2 = Available with Modifications
      1 = Under Development
      0 = Not Available                                                                              4. Ent Document Mgmt                                                       Page 50
APPENDIX F: 4. ENTERPRISE DOCUMENT MANAGEMENT


                    Comments




Key
3 = Currently Available Installed
2 = Available with Modifications
1 = Under Development
0 = Not Available                   4. Ent Document Mgmt   Page 51
APPENDIX F: 4. ENTERPRISE DOCUMENT MANAGEMENT


                    Comments




Key
3 = Currently Available Installed
2 = Available with Modifications
1 = Under Development
0 = Not Available                   4. Ent Document Mgmt   Page 52
APPENDIX F: 4. ENTERPRISE DOCUMENT MANAGEMENT


                    Comments




Key
3 = Currently Available Installed
2 = Available with Modifications
1 = Under Development
0 = Not Available                   4. Ent Document Mgmt   Page 53
APPENDIX F: 4. ENTERPRISE DOCUMENT MANAGEMENT


                    Comments




Key
3 = Currently Available Installed
2 = Available with Modifications
1 = Under Development
0 = Not Available                   4. Ent Document Mgmt   Page 54
APPENDIX F: 4. ENTERPRISE DOCUMENT MANAGEMENT


                    Comments




Key
3 = Currently Available Installed
2 = Available with Modifications
1 = Under Development
0 = Not Available                   4. Ent Document Mgmt   Page 55
APPENDIX F: 4. ENTERPRISE DOCUMENT MANAGEMENT


                    Comments




Key
3 = Currently Available Installed
2 = Available with Modifications
1 = Under Development
0 = Not Available                   4. Ent Document Mgmt   Page 56
APPENDIX F: 4. ENTERPRISE DOCUMENT MANAGEMENT


                    Comments




Key
3 = Currently Available Installed
2 = Available with Modifications
1 = Under Development
0 = Not Available                   4. Ent Document Mgmt   Page 57
APPENDIX F: 4. ENTERPRISE DOCUMENT MANAGEMENT


                    Comments




Key
3 = Currently Available Installed
2 = Available with Modifications
1 = Under Development
0 = Not Available                   4. Ent Document Mgmt   Page 58
APPENDIX F: 4. ENTERPRISE DOCUMENT MANAGEMENT


                    Comments




Key
3 = Currently Available Installed
2 = Available with Modifications
1 = Under Development
0 = Not Available                   4. Ent Document Mgmt   Page 59
APPENDIX F: 4. ENTERPRISE DOCUMENT MANAGEMENT


                    Comments




Key
3 = Currently Available Installed
2 = Available with Modifications
1 = Under Development
0 = Not Available                   4. Ent Document Mgmt   Page 60
APPENDIX F: 4. ENTERPRISE DOCUMENT MANAGEMENT


                    Comments




Key
3 = Currently Available Installed
2 = Available with Modifications
1 = Under Development
0 = Not Available                   4. Ent Document Mgmt   Page 61
APPENDIX F: 4. ENTERPRISE DOCUMENT MANAGEMENT


                    Comments




Key
3 = Currently Available Installed
2 = Available with Modifications
1 = Under Development
0 = Not Available                   4. Ent Document Mgmt   Page 62
      APPENDIX F: 5. PORTALS
                                                                                                                     Vendor
                                                                                                                  Response:
NO.                                       FUNCTIONAL REQUIREMENT
                                                                                                                   Availability     Est. Delivery   Additional
                                                                                                                  (3, 2, 1, or 0)        Date         Cost
      Physician Portal
 1    System supports secure web-enabled access to enhance access options and reduce maintenance
      expense (vs. being limited to VPN connectivity).
 2    System supports same user interface and real time access to same functionality/information in the
      office/hospital and remotely; i.e. ordering and results (incl. lab, pharmacy, radiology, ancillary)
      documentation, electronic signature, CDS, access to past history /medication & visit information, access
      to scanned documents and concurrent access.
 3    System shall provide the ability to remotely view wave form data downloaded from inpatient devices
 4    System supports customization of user interfaces and/or displays
 5    System portal is supported via mobile devices. Specify which devices are compatible.
 6    System portal supports secure/encrypted clinical messaging, including attaching documents and
      messaging receipt confirmations
 7    System supports secure/encrypted instant messaging among clinicians
 8    User can access on-line information via portal, including but not limited to:
      Directory, Policies and Procedures, Guidelines & Care Plans, Malpractice events "Lessons Learned",
      Formularies, CME, etc.
 9    System supports links/access to external on-line resources, including: Drug Reference database(s) for
      interactions/med recalls, medical information, etc.
10    System supports E-Signature for transcribed reports
11
      System allows clinician to view own schedule as well as viewing of assigned residents/PA/NP schedules
12    System supports easy, single sign-on
13    System provides the ability to launch to other systems from your portal seamlessly. Please describe your
      capabilities.
      Patient Portal
14    The system provides the ability for patients to view their electronic health record EHR remotely (via the
      Internet/portal).
15    Patients have the ability to update their electronic record remotely (personal health record-PHR) and
      update items may be customized by site.
16    System supports customization of user interfaces and/or displays
17    Patients can request and make appointments via the portal

      Key
      3 = Currently Available Installed
      2 = Available with Modifications
      1 = Under Development
      0 = Not Available                                                                                 5. Portals                                               Page63
      APPENDIX F: 5. PORTALS
                                                                                                                        Vendor
                                                                                                                     Response:
NO.                                       FUNCTIONAL REQUIREMENT
                                                                                                                      Availability     Est. Delivery   Additional
                                                                                                                     (3, 2, 1, or 0)        Date         Cost
      Patients can request medication refills via the portal
18    Patients have the ability to securely message their providers and receive responses. This
      correspondence is tracked in the clinical record.
19    Patients may make credit card, cash card and recurring payments on specified accounts via the portal
20    The system provides the ability to track if patients have 'opted in' for email communications.
21    The system shall provide secure messaging/email between the physician's office and patient.
22    System provides a full audit trail of all patient transactions
23    The system shall provide the ability to capture and explicitly label patient-originated data, including date
      and time of capture.
24    The system shall provide the ability to capture and label the source, date and time of clinical data
      provided on behalf of the patient.
25    System supports interfaces to home monitoring devices
26    Patients may self-register via kiosk in the hospital, clinic or other hospital-based setting




      Key
      3 = Currently Available Installed
      2 = Available with Modifications
      1 = Under Development
      0 = Not Available                                                                                      5. Portals                                             Page64
APPENDIX F: 5. PORTALS


                       Comments




Key
3 = Currently Available Installed
2 = Available with Modifications
1 = Under Development
0 = Not Available                   5. Portals   Page65
APPENDIX F: 5. PORTALS


                       Comments




Key
3 = Currently Available Installed
2 = Available with Modifications
1 = Under Development
0 = Not Available                   5. Portals   Page66
      APPENDIX F: 6. GLOBAL FUNCTIONS
                                                                                                                           Vendor
                                                                                                                        Response:
NO.                                       FUNCTIONAL REQUIREMENT
                                                                                                                         Availability     Est. Delivery   Additional
                                                                                                                        (3, 2, 1, or 0)        Date         Cost
      GLOBAL FUNCTIONS
      User-Defined Customizations
 1    System shall support the ability to customize screens within System, i.e., add data elements, indicate
      required, change layout, etc. without vendor assistance.
 2    System shall support the ability to customize all forms used within System without vendor assistance.

 3    System shall support the ability to create/customize various correspondence letters. Please indicate if
      this can be done by the client or if this requires vendor assistance.
      Security Access and Authentication
 4    System shall support user, role or context-based access rights.
 5    System shall have the ability to identify what department/location the user is associated with in the
      Security screen.
 6    System shall support restriction of specified users from designated patients‟ charts e.g., VIPs.
 7    System shall support confidential designation for certain note types, medications, tests, etc. with
      restricted access to authorized users.
 8    System shall support restricted locations, i.e., confidential locations
 9    System supports ability to lock program after a series of invalid log-in attempts.
10    System shall support flexible security rules by site or patient population.
11    System shall support password strength rules incl. minimum length (6 characters), alpha and numerics,
      case sensitive.
12    System shall support password expiration rules that are user definable.
13    System shall track edits made to passwords or user ids, inc. date, time and what was changed.
14    System allows for the assignment of multiple systems manager/systems administrator/root level accounts
      to facilitate auditing
15    System shall support the use of biometric and/or proximity/RFID mechanisms for password/sign-on.
16    System shall maintain a directory of all personnel who currently access/use System.
17    System shall maintain a directory of personnel external to the organization who are not users of System
      to facilitate communication and information exchange.
18    System shall support configurable time-out for inactivity, i.e., configurable by user, entity, and/or user-type

19    System shall provide locking priorities for data entry (i.e. two users cannot chart simultaneously
      except/save in the progress note section).
      Key
      3 = Currently Available Installed
      2 = Available with Modifications
      1 = Under Development
      0 = Not Available                                                                               6. Global Functions                                              Page 67
          APPENDIX F: 6. GLOBAL FUNCTIONS
                                                                                                                            Vendor
                                                                                                                         Response:
NO.                                           FUNCTIONAL REQUIREMENT
                                                                                                                          Availability     Est. Delivery   Additional
                                                                                                                         (3, 2, 1, or 0)        Date         Cost
20        System shall provide the ability to sign off a service from one provider to another at nights, weekends,
          and as needed
21        System shall provide the ability to suspend a session (lock-out) for easy return later to same access
          point. Suspend should also follow same time-out settings for user
22        System shall have security controls available to address HIPAA security requirements regarding
          electronic protected health information (EPHI) such as:
      a         Access controls for segmenting user or software programs access to information based on pre-
                defined or customized roles, functions, processes etc.
      b         Unique user identification (username or ID) for identification and tracking user identity
      c         Automatic log-off (down to the routine level) after a defined period of system inactivity, which may
                include user re-authentication to System. Can different applications be customized with their
                timeout parameters?
      d         Protections against unauthorized access and secure electronic transmission of data. Describe
                methods, including authentication and encryption, if available.
      e         Audit controls for recording and examining system activity (including viewing of records) which may
                include; user, function, process and/or content levels. Reportable by user, by patient or other
                reporting level with the ability to generate customized reports. Audit trails need to be able to track
                what function the user is using, for how long, what changes were made, before and after values, etc.


      f         Integrity and authentication controls to ensure data has not been improperly altered or destroyed
      g         Person or entity authentication to corroborate that a person or entity is who they claims to be which
                should include unique user identification and additional authentication control such as passwords,
                PIN, token or biometric, etc. Will System facilitate move to single sign-on technology without custom
                programming?
      h         Mechanisms for data backup, emergency operations and disaster recovery assuming a remote
                hosted/ASP model.
      i         Mechanisms for restricting and tracking changes to system hardware and software for a remote
                hosted/ASP model.
23        System shall support 'break-the-glass' access.
24        System allows definition of acceptable circumstances for users to bypass emergency access controls.

25        System requires a second level of validation before providing user emergency access.

          Key
          3 = Currently Available Installed
          2 = Available with Modifications
          1 = Under Development
          0 = Not Available                                                                              6. Global Functions                                            Page 68
      APPENDIX F: 6. GLOBAL FUNCTIONS
                                                                                                                    Vendor
                                                                                                                 Response:
NO.                                       FUNCTIONAL REQUIREMENT
                                                                                                                  Availability     Est. Delivery   Additional
                                                                                                                 (3, 2, 1, or 0)        Date         Cost
26    System can generate emergency access reports.

      Encrypted E-mail
27    System provides the ability to password protect/encrypt e-mails within and external to organization
      Establish encryption and decryption mechanism for ePHI, so as to render electronically stored data
28    unrecognizable health information.
29    Have audit controls implemented that allow an independent reviewer to review systems activities.
      Have person and entry authentication that verify the person seeking access to ePHI is the one claimed.
30

31    Have controls in place that ensures that the integrity of ePHI is maintained when in transit.
      Health Information Exchange (HIE)
32    System is able to fully participate in HIE transactions




      Key
      3 = Currently Available Installed
      2 = Available with Modifications
      1 = Under Development
      0 = Not Available                                                                               6. Global Functions                                       Page 69
APPENDIX F: 6. GLOBAL FUNCTIONS


                       Comments




Key
3 = Currently Available Installed
2 = Available with Modifications
1 = Under Development
0 = Not Available                   6. Global Functions   Page 70
APPENDIX F: 6. GLOBAL FUNCTIONS


                       Comments




Key
3 = Currently Available Installed
2 = Available with Modifications
1 = Under Development
0 = Not Available                   6. Global Functions   Page 71
APPENDIX F: 6. GLOBAL FUNCTIONS


                       Comments




Key
3 = Currently Available Installed
2 = Available with Modifications
1 = Under Development
0 = Not Available                   6. Global Functions   Page 72
     APPENDIX F: 7. HEALTH INFORMATION MANAGEMENT (HIM)
                                                                                                                        Vendor
                                                                                                                     Response:
                                         FUNCTIONAL REQUIREMENT
                                                                                                                      Availability     Est. Delivery   Additional
                                                                                                                     (3, 2, 1, or 0)        Date         Cost
       Health Information Management (HIM)
       Structure, set up and maintenance
       System shall provide centralized management of the structure and set up by the System Administrator or
1      other authorized personnel
2      System shall track the development and maintenance of all configurations over time.
       System will allow abiilty perform system maintenance, data integrity processes without downtime or
3      disruption to users. Describe process for system maintenance and data integrity.
       Chart Completion & Deficiency Management
4      System automatically notifies physicians of discharges, incomplete and delinquent charts . Please
       specify how this can be done. Electronic notifications will be encrypted.
5    System provides efficiency features to assist in chart completion:
   a      Launch from deficiency notice directly to appropriate document in patient‟s chart
   b      System flags to indicate components of chart that are incomplete/missing data
 6   System supports on-line eSignature for completions with dual authentication and transaction log.
 7   System supports user-defined parameters to create deficiency, e.g., eSignature 72 hours late
 8   System supports the customization and addition of deficiency options by system administrator.
 9   System has the ability to add messages to an incomplete chart utilizing messages
10   System supports user-defined triggers to determine who receives a warning vs.reminder letter vs.
     suspension letter
11     System can automatically update deficiency status upon completion of chart
12     System provides multiple customizable options to track deficiencies, e.g., by type of deficiency, provider,
       days outstanding, etc. Describe how system tracks deficiencies.
13     System supports work queues to manage deficiency tracking
14     System supports remote access for physicians access to reports/patient information
15     System can place physicians on suspension and monitor status
16     System provides user-customizable letters to support the suspension process for notification
17     System can interface a suspension flag to Registration/ADT system and CIS
18     System can automatically remove suspension flag from ADT/Registration system once deficiencies are
       corrected.
19     System provides customizable management reporting for tracking delinquencies, aging analysis,
       summary and by physician, suspension reports, probation reports, provider activity reports, etc.
20     System provides rapid and individual options for reviewing and updating record deficiences.
     Key
     3 = Currently Available Installed
     2 = Available with Modifications
     1 = Under Development
     0 = Not Available                                                                                     7. HIM                                                   Page 73
     APPENDIX F: 7. HEALTH INFORMATION MANAGEMENT (HIM)
                                                                                                                        Vendor
                                                                                                                     Response:
                                         FUNCTIONAL REQUIREMENT
                                                                                                                      Availability     Est. Delivery   Additional
                                                                                                                     (3, 2, 1, or 0)        Date         Cost
21     System will integrate with data warehouse, EDMS, or other respository. Describe electronic record
       systems that have been integrated with this system.
22     System shall allow email of physician deficiency notifications that are customizable to occur when
       deficiency is assigned or on a pre-defined schedule based on user defined critiera.
23     System shall be able to recognize additional providers identified on a document and email or notify them
       based on customizable criteria.
24     System shall be able to track physician deficiencies for purposes of reporting, suspension and
       customizable record management functions.
25     System shall have a customizable provider data table that will support deficiency tracking, status that can
       be easily integrated with systemwide provider profiles.
26     System has the ability to re-open a completed chart to flag deficiencies
27     System has ability to conduct a deficiency analysis at time patient is prepared for discharge
       Release of Information (ROI)
28     System provides support for disclosure management in compliance with HIPAA and applicable law.
       Please describe your system's capabilities.
29     System supports ability to document request for disclosure including type of information disclosed, when
       disclosed, and to whom information was disclosed, maintaining a transaction audit trail.
30     System provides alerts for records with approved amendments.
31     System provides customizable alerts that would identify records with restrictions, fraudulant requests,
       locked file records, etc. Describe how your system performs this function.
32     System provides the ability to define one or more reports as the legal medical record for disclosure
       purposes. Please explain.
33     System has ability to classify types of requests by user-defined criteria
34
       System has the ability to track incomplete requests and email designated individuals of aging requests.
35     System can track all outstanding requests sorted by user-defined criteria and/or requestor and email to
       designated individuals.
36     System alerts for duplicate requests, e.g., one already filled or one still incomplete and receiving second
       request
37     System supports user-definable invoice formats.
38     System supports customizable table for release requestors, addressees, record types, etc. Describe the
       release of information logging schema.

     Key
     3 = Currently Available Installed
     2 = Available with Modifications
     1 = Under Development
     0 = Not Available                                                                                      7. HIM                                                  Page 74
     APPENDIX F: 7. HEALTH INFORMATION MANAGEMENT (HIM)
                                                                                                                          Vendor
                                                                                                                       Response:
                                         FUNCTIONAL REQUIREMENT
                                                                                                                        Availability     Est. Delivery   Additional
                                                                                                                       (3, 2, 1, or 0)        Date         Cost
39
       System is able to generate an invoice for certain types of ROIs, e.g., attorneys, auditors, patients, etc.
40     System has ability to pend an ROI request until payment is received.
41     System can automatically trigger to release the pended ROI when payment is received
42     System can track unpaid invoices and prompts for timely re-billings
43     System supports user-customizable letters based on specific criteria, e.g., improper consent, no payment
       accompanying request, no records shown for this patient, etc.
44
       System supports automatic queing of the record from the EDMS when request is logged in to ROI system
45     Release of information module allows batch printing for selected documents to paper, CD, electronic file.
       Specify all out put media.
46     Release of information requests can be managed from within the ROI application while accessing
       documents stored in the EDMS. Describe the Release of Information application and workfflow.
47     Release of informaiton module includes automatic logging, flexible document selection process, and
       batch printing. Describe the release of information workflow
48     System supports multiple media output for ROI, e.g., paper, fax, Internet, CD, etc. Please specify.
       Extraction and Redaction
49
       The system will allow the creation of an exact replicate of an EDMS record, whereby sensitive information
       is hidden from view in the extract, while the originating record remains intact. The replicated document
       will retain history in metadata data, a transaction history which includes date, time, creator and reason for
       extract. Please describe process and sample document with extraction process demonstated.
50
       The system will create a navigable link between an extract (replicated document) and the original record
       from which is was taken. Such a link should preserve the relationship between the extract and the
       source record wihtout compromising the access and security controls applicable to the record.
       Other
51     System supports setup of work queues and ability to prioritize requests/actions within the queue.
52     System provides robust productivity management reporting. Describe and provide samples.
53     System provides robust reporting of all transactions during a documents lifecycle
54     System provides customizable reporting for all data elements available based on the document capture,
       storage process.

     Key
     3 = Currently Available Installed
     2 = Available with Modifications
     1 = Under Development
     0 = Not Available                                                                                       7. HIM                                                   Page 75
     APPENDIX F: 7. HEALTH INFORMATION MANAGEMENT (HIM)
                                                                                                                        Vendor
                                                                                                                     Response:
                                         FUNCTIONAL REQUIREMENT
                                                                                                                      Availability     Est. Delivery   Additional
                                                                                                                     (3, 2, 1, or 0)        Date         Cost
55     System provides reporting for accounting of disclosures
56     System provides flexible customizable report design. Describe process and specify any special report
       writers or vendor assistance required. Provide samples of reports.
       Quality Monitoring /Peer Review
57
       System provides workflow for peer review and quality monitoring with customizable fields and reporting.
58     System supports integrated/interface data imports/exports based on customizable user defimed fields.
59     System supports flexible adhoc data reporting for quality data
       Coding and Abstracting
60     System supports coding and abstracting work flow with user defined and user customizable abstracting
       fields
61     System shall support integration for coding and abstracting data elements to e-MPI, Finance and revenue
       cycle, data reporting sytems.
62
       System supports computer assisted coding - please describe how your system performs this function.
63     System vendor will support annual and incremental updates/maintenance to international and national
       classification systems and nomenclature
64
       System supports coding and classification resources including quick links to national coding resources
       and clinical decision support for code assignment, sequencing and revenue cycle enhancements.
65     System supports annotation, highlighting and "stick note" options for communication with others in
       relation to coding questions.
66     System will provide the creation of coding queries via query library or ad hoc reporting that can be
       electrnically generated, electroniically transmitted, electronically completed via e-form technologies and
       electronically signed with an email response to the requestor. Describe how your system would support
       his workflow.
67     System supports automation of coding work flow…eg. Computer-assisted coding.
68     System supports automated case assignment to work queues.
69     System supports user assignment of cases based on special attributes (eg. VIP, dollars or case type
       such as cancer or trauma, etc.).
70     System supports online communication between employees and managers.
71     System supports most industry standard encoders/groupers.

     Key
     3 = Currently Available Installed
     2 = Available with Modifications
     1 = Under Development
     0 = Not Available                                                                                      7. HIM                                                  Page 76
     APPENDIX F: 7. HEALTH INFORMATION MANAGEMENT (HIM)
                                                                                                                   Vendor
                                                                                                                Response:
                                         FUNCTIONAL REQUIREMENT
                                                                                                                 Availability     Est. Delivery   Additional
                                                                                                                (3, 2, 1, or 0)        Date         Cost
72     System support both on-site and remote coding activities.
73     System supports assignment of high-risk coding to supervisors…or…allows coding verification as staff
       complete cases.
74     System supports electronic query capability.
75     System contains tools for monitoring and evaluating the coding process.
76     System supports ICD-10-CM and/or ICD-10-PCS in addition to ICD-9-CM
77     System is compliant with Version 5010 transactions standards.
78     System supports General Equivalence Mappings for the ICD9 to ICD10 conversion process.




     Key
     3 = Currently Available Installed
     2 = Available with Modifications
     1 = Under Development
     0 = Not Available                                                                                 7. HIM                                                  Page 77
APPENDIX F: 7. HEALTH INFORMATION MANAGEMENT (HIM)


                       Comments




Key
3 = Currently Available Installed
2 = Available with Modifications
1 = Under Development
0 = Not Available                      7. HIM        Page 78
APPENDIX F: 7. HEALTH INFORMATION MANAGEMENT (HIM)


                       Comments




Key
3 = Currently Available Installed
2 = Available with Modifications
1 = Under Development
0 = Not Available                      7. HIM        Page 79
APPENDIX F: 7. HEALTH INFORMATION MANAGEMENT (HIM)


                       Comments




Key
3 = Currently Available Installed
2 = Available with Modifications
1 = Under Development
0 = Not Available                      7. HIM        Page 80
APPENDIX F: 7. HEALTH INFORMATION MANAGEMENT (HIM)


                       Comments




Key
3 = Currently Available Installed
2 = Available with Modifications
1 = Under Development
0 = Not Available                      7. HIM        Page 81
APPENDIX F: 7. HEALTH INFORMATION MANAGEMENT (HIM)


                       Comments




Key
3 = Currently Available Installed
2 = Available with Modifications
1 = Under Development
0 = Not Available                      7. HIM        Page 82
      APPENDIX F: 8. REPORTING TOOLS
                                                                                                                      Vendor
                                                                                                                   Response:
NO.                                       FUNCTIONAL REQUIREMENT
                                                                                                                    Availability     Est. Delivery   Additional
                                                                                                                   (3, 2, 1, or 0)        Date         Cost
      REPORTING TOOLS
 1    System must be able to export pre-defined data sets/ all data to Siemens Decision Support System data
      warehouse as well as other external entities and/or commercially available reporting tools.
 2    System has an internal or vendor recommended Report Writer that is used by all modules.
 3    All user defined data elements will be accessible on reports and be available for download/extraction.
 4    System shall provide the ability to store formats/queries of reports for repeatable use and 'publish' for
      access.
 5    System shall generate patient summary reports, i.e., consisting of all or part of an individual's medical
      record.
 6    System shall generate patient population reports e.g., diabetes roster.
 7    System shall provide the ability to specify report parameters (sort and filter criteria) based on patient
      demographic and clinical data (e.g., all male patients over 50 that are diabetic and have a HbA1c value of
      over 7.0 or that are on a certain medication).
      System shall provide the ability to specify report parameters (sort and filter criteria) based on the
      attending or service or department (e.g. all patients for that attending or department)
 8    System shall generate reports based on absence of clinical data element, e.g., a lab test has not been
      performed or a blood pressure has not been measured in the xx period of time.
 9    System shall generate complete, partial or summary patient record in hardcopy or electronic output.
10    System shall generate hardcopy and electronic output by activities and events on a chosen date and/or
      date range e.g., all hospital discharge summaries.
11    System shall create hardcopy and electronic report summary information (procedures, medications, labs,
      immunizations, allergies, and vital signs).
12    System shall provide the ability to de-identify protected health information (PHI) on the hardcopy and
      electronic output, but leave the actual PHI data unmodified in the original record.
13    Please include a full listing of standard reports available with each of your system's modules. Also,
      please include a sampling of those reports (some from each module proposed).
14    Vendor's data warehouse/reporting database allows the import of data from other systems with ability to
      rationalize and sync patient ID's, e.g., other clinical systems, patient accounting systems, etc.
15    System shall provide the ability to define one or more reports as the Legal Health Record for disclosure
      purposes.
16    System shall provide support for disclosure management in compliance with HIPAA and applicable law.
      Please describe your system's capabilities.
      Key
      3 = Currently Available Installed
      2 = Available with Modifications
      1 = Under Development
      0 = Not Available                                                                           8. Reporting Tools                                              Page 83
      APPENDIX F: 8. REPORTING TOOLS
                                                                                                                         Vendor
                                                                                                                      Response:
NO.                                       FUNCTIONAL REQUIREMENT
                                                                                                                       Availability     Est. Delivery   Additional
                                                                                                                      (3, 2, 1, or 0)        Date         Cost
17    System shall support graphical formats for reporting as part of the standard package.
18    Reporting database is separate from the production database to avoid response time issues when doing
      queries/printing.
19    System supports user defined reporting to support SMMC's Key Performance Indicators (KPIs).
20    System supports the incorporation of data from external sources
21    System supports end-user-friendly search capability for specific data, i.e., natural language search
22    System provides tools for developing and maintaining the data repository (adding/editing data elements)
      with minimal effort.
23    System allows data to be appended (with appropriate privileges)
24    System shall provide a document data model that serves as a foundation for defining and configuring the
      stored data elements
25    System supports storage and retrieval of data to support registry efforts (submission in acceptable
      formats), e.g., pediatric JCAHO Core Measures, immunizations, oncology, etc.
26    System shall provide the ability to view historical events and show historical trending
27    System supports a help function to show how to query for decision support and research
28    System shall provide the ability to create user-defined database views
29    System shall provide the ability to add new tables within the database
30    System shall support internal and external (JCAHO, CMS, Leapfrog, etc.) health care quality /cost-benefit
      / patient safety initiatives
31    System shall support SMMC-specific initiatives (e.g. study-specific data collection templates, etc.)
32    System shall provide the ability to mask patient data for reporting (both anonymous [no code number] and
      de-identified [some patient definers (age, sex, dx) but no identifiers], consistent with HIPAA requirements

33    System shall support the creation of registries (i.e., Chronic disease, Tumor registry, Implant Registry,
      Trauma, etc)
34    System shall provide the ability for retrospective, concurrent, and prospective data searching defined by
      user-defined criteria (i.e., by dates, diagnosis, etc.) for analyses of patient data
35    System shall provide the ability for the user to write own queries and search (patient records and
      databases) by an unlimited number of variables
36    System shall provide the ability for a report function that allows retaining ad hoc queries for user-specific
      use (i.e. password protected)


      Key
      3 = Currently Available Installed
      2 = Available with Modifications
      1 = Under Development
      0 = Not Available                                                                                8. Reporting Tools                                            Page 84
      APPENDIX F: 8. REPORTING TOOLS
                                                                                                                     Vendor
                                                                                                                  Response:
NO.                                       FUNCTIONAL REQUIREMENT
                                                                                                                   Availability     Est. Delivery   Additional
                                                                                                                  (3, 2, 1, or 0)        Date         Cost
37    System shall provide the ability to integrate internal clinical and financial data with data from foreign
      systems
38    System shall support ability for a single community-based view of patient care or patient trends across
      multiple systems to enable and improve healthcare forecasting, analyses, and visualization.
N/A   Specify any specific tools/software you offer (either native or 3rd party) to support data and content
      mining and/or predictive analytics (e.g., SAS, SPSS Predictive Analytics)




      Key
      3 = Currently Available Installed
      2 = Available with Modifications
      1 = Under Development
      0 = Not Available                                                                                8. Reporting Tools                                        Page 85
APPENDIX F: 8. REPORTING TOOLS


                       Comments




Key
3 = Currently Available Installed
2 = Available with Modifications
1 = Under Development
0 = Not Available                   8. Reporting Tools   Page 86
APPENDIX F: 8. REPORTING TOOLS


                       Comments




Key
3 = Currently Available Installed
2 = Available with Modifications
1 = Under Development
0 = Not Available                   8. Reporting Tools   Page 87
APPENDIX F: 8. REPORTING TOOLS


                       Comments




Key
3 = Currently Available Installed
2 = Available with Modifications
1 = Under Development
0 = Not Available                   8. Reporting Tools   Page 88
Appendix J: 9.: Pharmacy


                                                                                                       Vendor Response:
NO.                               FUNCTIONAL REQUIREMENT
                                                                                                            Availability     Est. Delivery
                                                                                                           (3, 2, 1, or 0)        Date     Additional Cost
      PHARMACY
      General System Functionality
 1    System shall provide the ability to toggle between patient records
 2    System shall provide the ability to implement bar code medication administration – BCMA
 3    System supports the use of RFID for administration and tracking purposes
 4    System supports eMAR usage across multiple departments, disciplines and across inpatient
      and outpatient continuum.
 5    System supports clinical decision support via alerts and bi-directional messaging including
      paging with providers
 6    System supports the maintenance of active physician/service rosters and flags physicians'
      ordering w/out hospital (or specific) privileges
 7    System shall provide detailed visit to visit (encounter) information related to medications
      (including Inpatient, Hospital Based Clinic, and Satellite Clinic visits).
 8    System provides the ability to reconcile home/outpatient meds with inpatient medications at
      time of admission, discharge and any changes in level of care.
 9    System supports active and inactive, inpatient and outpatient medication list (current and
      history up to 24 months). Describe how you propose to accomplish this across disparate
      systems for ED, ambulatory and inpatient settings.
 10   System shall provide the ability to track and report on medication usage/all controlled
      substances by user-defined variables
 11   System monitors the use of abbreviations and alerts for inappropriate abbreviations.
 12   System shall provide the ability to access protocols, verify if proper legal documents are in
      place (i.e., consent).
 13   System supports mapping of order catalog item to pharmacy dispensed product(s). This
      includes all doses and IVs.
 14   System supports differentiating look/sound alike medications (i.e. tall-man lettering, varied
      font colors, Soundex).
 15   System supports standalone medication lists and disease-specific medication lists
 16   System supports ability to check relevant lab values (i.e., creatinine clearance) and BSA, and
      send dose alerts based on abnormal values and redose based on the alert.
Appendix J: 9.: Pharmacy

 17   System shall have the ability to perform rounding calculations for pediatric/neonatal/bariatric
      dose calculation algorithms, e.g., milligrams and/or volume.
 18   System has the ability to interface with intermediaries to obtain patient's medication profile,
      e.g., SureScripts/RxHub.
 19   System shall support the ordering of insulin using a sliding scale/carbohydrate dosing
      protocols
 20   System shall provide the ability to support the management of investigational drugs.
 21   System shall provide the ability to flag patients in studies involving restricted/investigational
      medications and block charging for these medications.
 22   System shall provide the ability to enter a multi item, multi-ingredient TPN order with complex
      dosing levels and administration schedules
      Medication and Order Management
 23   System supports use of pharmacy alerts to manage formulary and drug therapy (restricted
      item, item requires P&T approval, No Longer Available, non-formulary, etc) Need both
      internal to pharmacy and for MD view.
 24   System shall automatically alert the ordering clinician if medication approval is needed
      (Example, medications such as Primaxin that need ID approval)
 25   System supports integration of pharmacy generated orders and modifications back to the
      eMAR from pharmacy specific order entry screens (e.g., RPh contacts MD to modify order).


 26   System shall provide the ability to provide automatic stop order alerts on eMAR for expired
      drugs.
 27   System supports the tracking of home medications and alerts if home medications are not
      reviewed by Pharmacy and/or not on hospital formulary.
 28   System supports the movement of medications from eMAR to discharge summary
 29   System shall provide the ability to flag/alert MD of need for co-signature for verbal orders
      initiated by the pharmacist and other messaging needs
 30
      System supports the ability to require documenting reasons for ordering specific medications
 31   System shall provide the ability to view physician's justification for override when pharmacy
      doesn't agree with the override
 32   System shall provide the ability to communicate order modification to the nurse and ordering
      physician.
 33   System shall provide the ability to hard-stop ordering and administration (inpatient) of a
      recalled drug
Appendix J: 9.: Pharmacy

 34   System shall provide the ability to create hard and soft stops for medication orders, with
      override, with audit trail of overrides
 35   System shall provide alternatives to non-formulary items, including dose
 36   Ability to queue non-formulary medication orders for review and approval.
 37   System supports automatic therapeutic substitution with ability to override
 38   System shall provide the ability to view all medication orders, flag new orders with pending
      status, and sort orders according to multiple variables
 39   System shall support double signatures for high risk medications (digoxin, indomethacin, K+,
      chemotherapy, narcotics, etc.)
 40   System supports Pharmacokinetic dosing programs
 41   System tracks expiration dates of medications at the time of inventory
 42   System supports chemo cumulative dosing for dose, episode, and lifetime level for
      chemotherapy monitoring
 43   System shall support ability to notify pharmacist of new medication orders via electronic
      messaging or paging (to support decentralized pharmacists)
 44   System shall have the ability to support reverse allergy checking when new allergies entered
      with active orders in place.
      Order Processing by RPh
 45   System shall provide the ability to support mandatory verification for selected medications
 46   System supports use of Sig abbreviations when inputting drug transactions. The
      abbreviations are expanded before updating the patient‟s profile.
 47   System shall allow for a customizable pharmacist verification function following non-
      pharmacist entry to transfer an order from non-verified to active/verified status.
 48   System shall support 'break-the-glass' security to allow processing if medication has not
      been verified.
 49   System supports ability for user-defined sort sequence and filters to process orders (sort by
      patient, by patient care unit, by order type (stat, routine), etc
 50   System supports ability for user-defined information to attach to dispensing item (e.g., attach
      eMAR message)
 51   System supports work lists for pharmacy staff with user-defined alerts.
 52   System shall provide the ability to have inbound orders for pharmacist verification display in
      the work queue sorted by user-defined rules based on drug, therapeutic class, route, „stat‟ or
      „now‟ flag, or patient location. Visual or auditory alerts are provided.
 53   System shall support charging dispensed-on-demand medications such as IV bags and
      alerts pharmacy to send the next dose based on it due date and time.
Appendix J: 9.: Pharmacy

           Clinical Decision Support
 54        System supports automatic therapeutic substitution with ability to override
 55        System supports chemo cumulative dosing for dose, episode, and lifetime level for
           chemotherapy monitoring
 56        System shall have the ability to support reverse allergy checking when new allergies are
           entered with active orders in place
 57        Supports the ability to provide user defined therapeutic alerts (e.g. high alert meds, look/
           sound alike, etc.)
 58        System shall support pediatric and bariatric weight-based volume dosing calculations, (per
           kilo, per square, customizable).
 59        System supports automatic age and weight based dosing, e.g. tiered Peds, Geriatrics.
 60        System supports ability to check relevant lab values (i.e., creatinine clearance) and BSA, and
           send dose alerts based on abnormal values and redose based on the alert.
 61        Supports the ability to use First Databank, Medi-span or other third party medication content

 62        Supports the ability to perform complete drug checking for:
      a      require allergy information before order able to be completed
      b      drug interaction checking with different severity levels
      c      drug-drug interaction checking
      d      drug-allergy interaction checking
      e      drug-food interaction checking
      f      drug-disease interaction checking
      g      allergy severity determination
      h      therapeutic duplication checking
       i     min-max dosing
 63        Supports the ability to override interaction warnings (depending on user level)
 64        Supports the ability to require documentation when overriding interactions
 65        System shall provide ability to set criticality of alerts (severe, intermediate, minor) by user
           type.
 68        System supports clinical decision support via alerts and bi-directional messaging including
           paging with providers
 66        System shall provide drug-specific instructions on the eMAR based on order sets with over-
           rides available
Appendix J: 9.: Pharmacy

 67   System supports ability to test alerts in live environment prior to activation (e.g., during
      "evaluation," alerts run in background without prompting physician during CPOE). Allows
      assessment of frequency and validity in "real-world".
 68   System supports surveillance process – automated medication error reporting system
      (anonymous, on-line report about suspected ADEs)
 69   System shall provide the ability to identify & report ADEs by individual entities, areas,
      providers, etc.
      Distribution Management
 70   System supports full functionality of unit dose distribution systems including closed loop bar-
      coding features. Please describe.
 71   System supports customization of administration times by patient care area, facility, clinical
      service, patient, and medication.
 72   System supports capability for single dose replacement without altering existing profile (e.g.,
      dropped/lost doses, etc.)
 73   System supports batch processing of medication and solutions for distribution
 74   System supports anti-diversionary feature. What vendors have you worked with on this?
      Label Generation
 75   System shall provide the ability to print label by batch or by demand, sorting by station, item,
      and user specified (e.g., from patient profile)
 76   System supports ability to print on more than one printer as part of report definition and re-
      direct print job when needed
 77   System supports customized medication label content and format defined by location and
      product type (i.e. volume, total protein, calorie, electrolytes per container)
 78   System provides IV label sequence printing by time, room, shift time
 79   System supports multiple label types and printers; For example, fonts, templates, sizes, NCR
      labels on dot matrix, thermal, zebra or laser printers
 80   System supports ability to re-print labels without charge generation
 81   System shall be capable of producing bar code label for every dose
      Formulary Management and Inventory
 82   System shall provide the ability to automatically adjust the pharmacy production schedule
      when an IV bag is charted
 83   System supports facility specific formulary (aka medication dispensing list)
 84   System shall provide the ability to deactivate or delete a formulary item and show impact on
      existing orders
Appendix J: 9.: Pharmacy

 85        System shall provide the ability to record vaccination lot numbers, manufacturer, and
           expiration date.
 86        System shall be able to track lot numbers for IV medications.
 87        System shall have the ability to access full drug database, e. g. First Databank, if medication
           not in hospital formulary and indicate as 'override and/or exception'.
 88        System supports name fields requiring the inclusion of generic fields for multiple synonyms
           (i.e., trade names)
 89        System supports functionality with automated dispensing cabinets, such as Pyxis
 90        System supports ability to make formulary changes effective immediately or on a specified
           future date
 91        System provides a report of all adds/edits/deletes from the formulary for use in synchronizing
           codes in the billing system
 92        System shall provide the ability for input of manufactured, compounding and prepackaged
           medications.
 93        System shall provide the ability to link compounded medications to NDCs to support alerts.

 94        System has the ability to enter new pricing formulas which use:
      a             Cost basis of actual or AWP
      b             Number of doses
      c             Number of dispensing units
      d             % mark-ups
      e             Mark-up amounts
      f             Dispensing fees
      g             Minimum/maximum charge
      h             Separate pricing for take home meds
       i            Pricing by dosing formulas
       j            Pricing based on type of patient (IP/OP) and payor
 95        System has the ability to store 'no charge' items, e.g., aspirin, Tylenol, yet maintain price in
           inventory file.
 96        System has the ability to round to the nearest nickel for any calculations done.
 97        System supports the ability to affect an overall price increase based on specific date. Please
           explain.
 98        Inventory Database maintains a Common Drug Name, Generic Drug Name and an Inventory
           Drug Name.
 98        System allows calculation of charges down to the tablet.
 99        Supports inventory management, including the:
Appendix J: 9.: Pharmacy

       a     ability to auto track perpetual inventory
       b     ability to flag formulary and non-formulary items
       c     ability to utilize J CODES as well as Medi-Cal codes
       d     ability to accept price updates automatically from external vendor
       e     ability to flag medication locations (floor stock, night cabinet, pharmacy, etc)
       f     ability to auto replenish inventory
       g     ability to auto receive orders from vendors
       h     ability to calculate total dosage from amt of units dispensed, and vice versa
           Charge Processing
 100       System requires "bill on chart" drugs to have an existing order before a transaction from the
           Clinical System to the Patient Billing System is allowed.

 101       System can be configured so that only specified drugs can be set to 'bill on chart'.
 102       System shall provide the ability to require that drug numbers be checked against
           organization's drug inventory database for those that are chargeable and those that are
           stocked. Inactive drugs are not chargeable.
 103       System provides the capability to credit patient account via bar code wand.
 104       System has the ability to test credits against what has been previously charged.
 105       Charge processing will collect dose, diagnosis, lab values, NDC and transmit to billing for
           processing formulary and non-formulary items
 106       System supports compliance with regulatory requirements for billing
 107       System shall have mechanisms that reconcile doses dispensed, administered and charged
           before bills are cut
 108       System shall support multiple charging mechanisms - Charging on administration or
           dispensing and on daily basis
 109
           System can prevent entry of charge data in the future or old date that is no longer appropriate
 110       System supports the capture of ICD9 codes (future ICD10) tied to specific medications
           (immuno-globin, chemo meds) based on Medicare's reimbursement policies. Please explain
           how this is handled.
           Additional Requirements
 111       System supports thumbprint biometrics and/or card reader and password user verification
 112       System shall provide the ability to build/create flexible fill lists (by nursing units, groups of
           units, or by dispense modality)
 113       System shall provide the ability to change medication route (PO to IV or vice versa) when a
           patient's dietary status changes.
Appendix J: 9.: Pharmacy

 114       System shall provide the ability to auto generate a report of patients transferred (and their
           medications) before carts are filled
 115       System shall provide the ability to support multiple cart fill times and frequencies
 116       System shall provide the ability to generate a report on a routine cart fill list.
 117       System shall provide the ability to notify the pharmacist a consult has been ordered
 118       System shall provide the ability to include supplemental information/administration guidelines
           on an order, eMAR and label.
 119       System shall provide the ability for extemporaneous oral syringe dosing and labeling.
 120       System shall provide the ability to manually charge per dose.
 121       System shall provide the ability to show fields for building medications: LVP, Piggyback, PO.

 122       System shall provide the ability to establish where and how an item is stocked (e.g. floor
           stocked items, Emergency trays)
 123       System shall provide the ability to view history and source of orders (RN vs. MD) including
           provider pager number
 124       System shall provide the ability to display non-medication orders and inter disciplinary
           documentation within the pharmacy application.
 125       System shall provide the ability to scan product and pharmacy employee barcodes to
           track/log dispensing process for pharmacy workflow and audit purposes.
 126       System shall provide the ability to change IV rates and have pharmacy IV batching
           automatically update
 127       System shall provide the ability to support reporting on non-formulary medications (i.e. cost,
           usage)
 128       System shall have the ability to generate a medication calendar from the discharge
           medication list or the inpatient medication list to enhance patient compliance.
 129       System shall have the ability to provide productivity reports, such as workload by function,
           shift, personnel
 130       Supports ability to access immunization registry
           Reporting
 131       System shall provide the ability to generate standard and ad-hoc reports (management and
           financial) e.g., drug usage, costs, by user defined variables.
 132       System supports the following types of reports (at a minimum):
       a        Daily Reports, e.g., Daily Workload including doses filled and orders filled, Daily
                Medication Updates, Daily IV Dispensing, Transaction Logs, Worklist of all unverified
                orders, etc.
Appendix J: 9.: Pharmacy

       b        Intervention Reporting, e.g., interventions performed, prioritized worklists for intervention
                follow-up/monitoring, IV to PO conversions, therapeutic equivalents, antibiotic dosing
                and heparin dosing and tracking costs of substitutions.
       c        Drug Utilization Reporting including formulary and non-formulary, e.g., statistical
                information, specific and generic reporting, by unit, by diagnosis
       d        Drug Utilization Trends by patient demographics and/or medical conditions, e.g.,
                identifying changes in medication usage to improve quality and/or provide more cost
                effective care.
       e        Formulary Drug List(s) (sorted a variety of ways, e.g., master list by NDC number, etc.)

       f        Inventory Management Reports, e.g., Annual inventory valuation, Inventory by
                manufacturer, Floor Stock by location, by drug, Restocking lists, etc.
       g        Cost Reports (purchased and/or dispensed)
       h        Medication Usage Pattern Reports, e.g., by accounting period , for last 12 months,
                specific medication usage over a user-defined specified time, etc.
       i        Dispensing/Administration Variance Reports
       j        Audit Reports, e.g., collect and report on all changes to orders and/or overrides of alerts

       k        State and Federal Regulatory Reporting, e.g., controlled substances, Public Health
                requirements, CDC requirements, JCAHO utilization reporting requirements, etc.
       l        Pharmacy Quality Measures Reporting, e.g., Pharmacy Quality Alliance: Measure
                Category: Patient Safety - Therapeutic Duplication, Overuse; Measure Category:
                Appropriate Use – Technique, Appropriate Drug Selection, National Quality Forum
                (NQF) Measures, etc.
       m        eMAR Reporting, e.g., override reports from eMAR, reconciliation reports between
                eMAR and what was actually done or delayed, etc.
       n         Technician IV Summary Sheet by Nursing Station
       o         Floor Stock Emergency Use Drug List by Dept
       p         Track and report Medication Recalls at the Patient Level
 133       Ability to capture required data to support UHC PSN (Patient Safety Net) reporting and
           extracts to populate PSN web-based system.
 134       Ability to route printed or electronic output to variable printers/devices
 135       Describe your mechanism for consolidating a view of medications to facilitate medication
           reconciliation between disparate ambulatory, ED and inpatient software solutions.
Appendix J: 9.: Pharmacy



       Comments
Appendix J: 9.: Pharmacy
Appendix J: 9.: Pharmacy
Appendix J: 9.: Pharmacy
Appendix J: 9.: Pharmacy
Appendix J: 9.: Pharmacy
Appendix J: 9.: Pharmacy
Appendix J: 9.: Pharmacy

				
DOCUMENT INFO
censhunay censhunay http://
About