AWHONN EDGE™ Benchmarking Database
Technical Requirements & FAQs
Requirements
Frequently Asked Questions
- Is the database network-based or stand-alone?
- If networked, does the server reside inside or outside the hospital firewall?
- Are interfaces involved?
- What are the implications of changing our EMR in the future?
- What technical support is available?
- What is the purchase process, including installation?
- How does our data populate the benchmarking database?
What are the bandwidth requirements?
500K to 2 MB per month
What are the Electronic Medical Record (EMR) requirements?
A hospital must use the following EMR systems:
- GE Perinatal Centricity (formerly QS): Site-tailorable or pre-configured.
- Philips OB TraceVue: All versions; must use an external database.
- Hill-Rom WatchChild: All current versions
For other EMRs, we will work with you and your vendor to derive the data set needed to participate.
What are the server requirements at my facility?
Server space provided by the hospital must have access to the EMR database for the data extraction application. Minimum system recommendations:
Operating System: Windows 2000, Windows XP, Windows Server 2003
Processor: Pentium II 300 MHZ
RAM: 128 MB
Disk Space: 400 MB (250 MB required for installation)
What version of Java, IE, Active X, XML, Microsoft Data Access Controls (MDAC) and .net are required?
- Internet Explorer version 7.0 (preferred but can accommodate 6.0)
- .net version 2.0
- No Java, Active X, XML or MDAC requirements
Is the database network-based or stand-alone?
A stand-alone database and website residing on Strategic Thinking Industries, LLC (STI) servers. Data from your hospital is sent via secure channels to STI servers.
If networked, does the server reside inside or outside the hospital firewall?
Outside
Are interfaces involved?
If so, what are the implications of changing our EMR in the future?
The AWHONN EDGE™ is a stand-alone database and website residing on STI servers.
Data is extracted from your EMR or by a query provided by STI and that extract is transmitted monthly to the STI servers.
If you convert to a different EMR, we will use another STI query or an extract query built by your IT group. When you migrate to another system, the AWHONN EDGE™ Benchmarking Database can lend itself as a data mart/warehouse of sorts, providing a seamless view of labor and delivery statistics.
What technical support is available?
STI provides technical support for the extract process, loading of data into the benchmarking database, and use of the benchmarking website.
What is the purchase process, including getting started and installation?
Purchase
Once a facility (or system) chooses to participate, they enter into an annual licensing agreement with AWHONN and a Business Associate Agreement with STI. The contract outlines each party’s responsibilities and associated fees.
Request a Contract
202-261-2415
Get Started
Once AWHONN receives the signed contract and fees, we schedule a kick-off meeting to begin the installation and set-up phase.
Installation
The installation and set-up process takes approximately six weeks but is considered a one-time process unless the hospital changes EMR systems. The timing is approximate and may vary depending on availability of the hospital's participants
Set Up: Weeks 1-3
1. Start the Technical Extraction Process
a. Obtain VPN access
b. Configure extract queries with hospital
2. Install & Configure Extraction Software
a. Map benchmarking items with hospital EMR
b. Install software and review initial extract
3. Review AWHONN Benchmarking Website
a. Initial logon and tour
b. Configure demographic preferences
Set Up: Weeks 4-6
4. Continue Extraction Process
a. Review load results into database staging area
5. Review AWHONN EDGE™ Benchmarking Website
a. Configure AWHONN column mapping
b. Report navigation overview
Once the extraction tool is in place, how does our data populate the benchmarking database?
The data population occurs in two distinct steps.
Step 1: Send Hospital EMR Data to AWHONN Staging:
Hospital's data is loaded to a "staging table"
Hospital receives "data gaps" report of missing items and gaps
Hospital maps new clinical categories to standard AWHONN items
Step 2: Populate the AWHONN EDGE™ Benchmarking Database
Each hospital's "staged data" is loaded into AWHONN EDGE™
Includes "clinical mapping" of hospital's custom items to AWHONN standard items
Hospital contact receives email notification of database population.
| More Information |  |
Legislative