282 lines
No EOL
23 KiB
HTML
282 lines
No EOL
23 KiB
HTML
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
|
|
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
|
<html xmlns="http://www.w3.org/1999/xhtml">
|
|
<head>
|
|
<title>Emergency Preparedness Resource Inventory (EPRI)--A Tool for Local, Regional, and State Planners: Part 2. Technical Manual, Chapter 4</title>
|
|
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
|
|
|
|
<!-- "metadata" -->
|
|
<meta name="description" content="The EPRI tool aids local or regional planners to assemble an inventory of critical resources that would be useful in responding to a bioterrorist attack." />
|
|
<meta name="keywords" content="Agency for Health Care Policy and Research, Agency for Healthcare Research and Quality, AHRQ, AHCPR, bioterrorism, community resources, disaster preparedness, emergency, hospital, mass casualty event, public health, surge capacity, urgent care" />
|
|
|
|
<link href="/includes/archive.css" rel="stylesheet" type="text/css" />
|
|
<link href="/includes/ahrqstyleprint_arch.css" rel="stylesheet" type="text/css" media="print" />
|
|
<script>
|
|
(function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){
|
|
(i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o),
|
|
m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m)
|
|
})(window,document,'script','//www.google-analytics.com/analytics.js','ga');
|
|
|
|
ga('create', 'UA-75759936-1', 'auto');
|
|
ga(' set', 'anonymizeIp', true);
|
|
|
|
ga('send', 'pageview');
|
|
|
|
</script></head><body><!-- Google Tag Manager -->
|
|
<noscript><iframe src="//www.googletagmanager.com/ns.html?id=GTM-W4DST4"
|
|
height="0" width="0" style="display:none;visibility:hidden"></iframe></noscript>
|
|
<script>(function(w,d,s,l,i){w[l]=w[l]||[];w[l].push({'gtm.start':
|
|
new Date().getTime(),event:'gtm.js'});var f=d.getElementsByTagName(s)[0],
|
|
j=d.createElement(s),dl=l!='dataLayer'?'&l='+l:'';j.async=true;j.src=
|
|
'//www.googletagmanager.com/gtm.js?id='+i+dl;f.parentNode.insertBefore(j,f);
|
|
})(window,document,'script','dataLayer','GTM-W4DST4');</script>
|
|
<!-- End Google Tag Manager -->
|
|
<noscript>
|
|
Your browser doesn't support JavaScript. Please upgrade to a modern browser or enable JavaScript in your existing browser.
|
|
</noscript>
|
|
|
|
<!-- Page Header v2.0 -->
|
|
<a name="top" id="top"></a>
|
|
<!--Begin Banner CodeS-->
|
|
<div id="ahrqbanner">
|
|
<div class="hhsportion">
|
|
<a href="#h1" class="skipnav">Skip Navigation</a>
|
|
<a href="http://www.hhs.gov" title="U.S. Department of Health and Human Services">
|
|
<img src="/images/hhs_banner.gif" alt="U.S. Department of Health and Human Services" />
|
|
</a>
|
|
<a href="http://www.hhs.gov" title="www.hhs.gov" class="hhsright">
|
|
<img src="/images/hhs_link.gif" alt="www.hhs.gov" />
|
|
</a>
|
|
</div>
|
|
|
|
<div class="ahrqportion">
|
|
<a href="/" title="Archive: Agency for Healthcare Research Quality">
|
|
<img src="/images/ahrq_banner.gif" alt="Agency for Healthcare Research Quality" />
|
|
</a><form name="searchForm" method="get" action="https://search.ahrq.gov/search" id="banner_searchform">
|
|
<label for="search" style="z-index:-1;position:relative;margin-right:-65px; font-size:0px;">Search</label>
|
|
<input name="q" type="text" value=" Search Archive" size="11" onfocus="this.value='';" class="gotext" label="Search archive" id="search" />
|
|
<input type="hidden" name="entqr" value="0" />
|
|
<input type="hidden" name="output" value="xml_no_dtd" />
|
|
<input type="hidden" name="proxystylesheet" value="ARCHIVE_Front_End" />
|
|
<input type="hidden" name="client" value="ARCHIVE_Front_End" />
|
|
<input type="hidden" name="site" value="ARCHIVE_AHRQ_GOV" />
|
|
<input src="/images/topbn_GoButton.gif" class="gobtn" name="Submit" onclick="javascript:document.searchForm.submit();" type="image" alt="Search" />
|
|
</form>
|
|
<a href="https://www.ahrq.gov/" class="ahrqright">www.ahrq.gov</a>
|
|
</div><div class="ahrqlinks"><a href="https://www.ahrq.gov/">AHRQ Home—Live Site</a> | <a href="/">Archive Home</a> | <a href="/sitemap.htm">Site Map</a> <!-- | <img src="/images/envelope1.jpg" alt="" width="21" height="14" /><a href="https://subscriptions.ahrq.gov/service/multi_subscribe.html?code=USAHRQ">E-mail Updates</a> --></div>
|
|
</div>
|
|
<div id="PrintBanner">
|
|
<img src="/images/printbanner_arch.jpg" alt="Archive print banner" />
|
|
</div>
|
|
<a name="h1"></a>
|
|
<!-- End banner code -->
|
|
<!-- End of Page header -->
|
|
|
|
<!-- Content Body -->
|
|
<div id="mainContent">
|
|
<table width="100%" border="0" cellspacing="0" cellpadding="0" >
|
|
<tr valign="top">
|
|
<td width="70%">
|
|
<!-- Center Content section -->
|
|
<table width="100%" border="0" cellpadding="0" cellspacing="0" style="margin-left:10px; margin-right:10px;margin-top:5px" summary="This table gives the layout format of the bread crumb area and the center content area.">
|
|
<!--DWLayoutTable-->
|
|
<tr>
|
|
<td class="crumb_link"><div id="crumbContent">
|
|
<p><strong>You Are Here:</strong> <span class="crumb_link"><a href="/" class="crumb_link">AHRQ Archive Home</a> > <a href="/research/epri/index.html" class="crumb_link">Emergency Preparedness Resource Inventory (EPRI)</a> > <a href="." class="crumb_link">Technical Manual</a> > Chapter 4</span></p>
|
|
</div>
|
|
</td>
|
|
</tr>
|
|
<tr>
|
|
<td height="30px"><span class="title"><a name="h1" id="h1"></a><h4>Emergency Preparedness Resource Inventory (EPRI)</h4> </span></td>
|
|
</tr>
|
|
<tr>
|
|
<td><div id="centerContent">
|
|
<div class="headnote">
|
|
<p>This information is for reference purposes only. It was current when produced and may now be outdated. Archive material is no longer maintained, and some links may not work. Persons with disabilities having difficulty accessing this information should contact us at: <a href="https://info.ahrq.gov/">https://info.ahrq.gov</a>. Let us know the nature of the problem, the Web address of what you want, and your contact information. </p>
|
|
|
|
|
|
<p>Please go to <a href="https://www.ahrq.gov/">www.ahrq.gov</a> for current information.</p></div>
|
|
|
|
<a id="User" name="User" />
|
|
<h2>4. User Registration Process </h2>
|
|
|
|
<p>Before explaining in <a href="#Users">Sections 4.3</a> and <a href="#Registration">4.4</a> how to provide authorized users with access to EPRI, two EPRI constructs must be explained: organizations (<a href="#Organizations">Section 4.1</a>) and locations (<a href="#Locations">Section 4.2</a>). In brief: </p>
|
|
<ul>
|
|
<li>There is a many-to-one relationship between locations and organizations (i.e., an organization can have multiple locations associated with it; a location is associated with one and only one organization).</li>
|
|
<li>There is a many-to-one relationship between users and organizations (i.e., an organization can have multiple users associated with it; a user is associated with one and only one organization).</li>
|
|
</ul>
|
|
|
|
<p>Various organization/location/user configurations can be set up in EPRI: </p>
|
|
<ul>
|
|
<li>An organization can control resources at a single location and have one user responsible for entering inventory data. This is the most common circumstance.</li>
|
|
<li>An organization can control resources at multiple locations and have one user responsible for entering inventory data for all the locations. For example, a fire department may have three fire stations, but one person at the main headquarters enters data for all three.</li>
|
|
<li>An organization can control resources at multiple locations and have multiple persons with data entry responsibility. To continue the example, each of the three fire stations may instead designate their own data entry person.</li>
|
|
<li>An organization can control resources at one (or multiple) locations but not have any users of the system. In this case, the organization administering EPRI will do data entry for this organization. If none of the fire stations has Internet access, data forms will need to be faxed out; EPRI staff will do the data entry upon receiving the faxes back from the fire stations.</li>
|
|
<li>An organization does not control any resources; users associated with this organization only run reports. For example, the director of planning for a State office of homeland security may wish to run reports, but his/her office building (location) has no resources to offer for emergency response.</li>
|
|
</ul>
|
|
|
|
<p>Organizations, locations, and users can be added to EPRI in two different ways: </p>
|
|
<ol>
|
|
<li>There are separate Web pages for organizations, locations, and users. Each Web page has an 'add and delete' function. </li>
|
|
<li>In the case of an organization that has a single location and a single user (a common situation in our pilot project), the system administrator can use a "registration wizard" to add the new organization, location, and user (<a href="#Registration">Section 4.4</a>). </li>
|
|
</ol>
|
|
|
|
<a id="Organizations" name="Organizations" />
|
|
<h3>Organizations</h3>
|
|
<a id="fig6" name="fig6" />
|
|
<p>The system administrator can add (by clicking "Add New") and delete (by clicking an 'X') organizations on the Organization Page, which is accessible by clicking 'Manage Organizations' on the system administrator's home page (<a href="eprimf6.htm">Figure 6</a>, 23 KB).<sup><a href="#six">6</a></sup> </p>
|
|
|
|
<p>The attributes of each organization are: </p>
|
|
<ul>
|
|
<li>Organization Name. </li>
|
|
<li>Data Enterer? A Yes/No field indicating whether the organization will be entering data on the resources they control. In our pilot project, some organizations controlling resources did not have Internet access, so we entered data for them. </li>
|
|
<li>Resource Owner? A Yes/No field indicating whether the organization controls resources. As noted earlier in this section, an organization may have users that only access reports. </li>
|
|
</ul>
|
|
|
|
<hr />
|
|
<p class="size2"><sup><a id="six" name="six">6</a></sup> All organization, location, and user names in the screen shots are fictitious. </p>
|
|
|
|
<hr />
|
|
<p class="size2"><a href="index.html#contents">Return to Contents</a></p>
|
|
|
|
<a id="Locations" name="Locations" />
|
|
<h3>Locations</h3>
|
|
<p>After an organization has been defined, locations associated with the organization can be entered. Location information can be entered by using either:</p>
|
|
|
|
<ul>
|
|
<li>The Location page (accessible by clicking "Locations" on the top menu bar or by clicking "Manage Locations" on the system administrator's home page)</li>
|
|
<li>The registration wizard (accessible by clicking "New Location/User Wizard" on the system administrator's home page). The wizard is discussed in <a href="#Registration">Section 4.4</a>. </li>
|
|
</ul>
|
|
|
|
<p>System administrators can add new locations. In addition, the Data Manager associated with an organization (see the discussion of "Input Roles" in <a href="#Users">Section 4.3</a>) can add a new location that is associated with his/her organization. </p>
|
|
|
|
<a id="fig7" name="fig7" />
|
|
<p>The system administrator can see a list of all locations that have been entered on the Location Page (<a href="eprimf7.htm">Figure 7</a>, 31 KB). </p>
|
|
|
|
<p>The attributes of each location are: </p>
|
|
<ul>
|
|
<li>Name. </li>
|
|
<li>Location Type. The drop down list contains all the location types entered on the Location Type Page (<a href="epriman3.htm#Location">Section 3.2</a>). </li>
|
|
<li>Organization Entering Data. Typically, this is the same as the organization that controls the resources, but another organization can also be specified (e.g., if an organization does not have Internet access, the system administrator's organization would likely be specified as the Organization Entering Data). When logged in as the system administrator, the drop down list contains all the organizations entered on the Organization Page (<a href="epriman3.htm#Setup">Section 3.1</a>); when logged in as an organization's data manager (<a href="epriman4.htm#Users">Section 4.3</a>), the drop down list only contains the data manager's organization. </li>
|
|
<li>Organization Controlling Resources. When logged in as the system administrator, the drop down list contains all the organizations entered on the Organization Page (<a href="epriman3.htm#Setup">Section 3.1</a>); when logged in as an organization's data manager (<a href="epriman4.htm#Users">Section 4.3</a>), the drop down list only contains the data manager's organization. </li>
|
|
<li>Address.</li>
|
|
<li>City. The drop down list contains all the cities imported into the database (<a href="epriman3.htm#Geography">Section 3.4</a>).</li>
|
|
<li>State. The drop down list contains all the States imported into the database (<a href="epriman3.htm#Geography">Section 3.4</a>).</li>
|
|
<li>Zip Code. The drop down list contains all the ZIP codes imported into the database (<a href="epriman3.htm#Geography">Section 3.4</a>).</li>
|
|
<li>County. The drop down list contains all the counties imported into the database (<a href="epriman3.htm#Geography">Section 3.4</a>).</li>
|
|
<li>Latitude/longitude. The latitude and longitude fields can be specified in three different ways:
|
|
<ul>
|
|
<li>If EPRI's subscription account with the Web Services vendor ESRI is active (<a href="epriman3.htm#MappingSetup">Section 3.5</a>), ESRI will return the latitude and longitude associated with the location's address (assuming it is a valid address) when the user clicks the "Get Latitude and Longitude" button. </li>
|
|
<li>If EPRI's ESRI account is not active, but, as part of the setup and customization process, latitude and longitude data were imported into the ZIP code table (<a href="epriman3.htm#Geography">Section 3.4</a>), the latitude and longitude values of the location are set equal to the latitude and longitude of the location's ZIP code once the user clicks the "Get Latitude and Longitude" button. </li>
|
|
<li>If more precise latitude and longitude values are known for the location, the user can enter these values directly on the Location page. </li>
|
|
</ul></li>
|
|
<li>Emergency Contact Name/Phone/Fax/E-mail. Each location can have an emergency contact person. In our pilot project, this person was typically not a user of EPRI, but rather someone who could be contacted on short notice at the location. </li>
|
|
<li>Active? Indicates whether the location is currently active in EPRI. This field is not currently used. </li>
|
|
<li>% complete. The Location Page contains a computed field that equals the percentage of nonemergency data entry fields filled in divided by the total number of non-emergency data entry fields for this location. </li>
|
|
<li>Check box. At the end of each line on the Location Page is a check box that is used to select locations to which to send an E-mail (<a href="epriman7.htm#Monitoring">Section 7.1</a>). </li>
|
|
</ul>
|
|
|
|
<p class="size2"><a href="index.html#contents">Return to Contents</a></p>
|
|
|
|
<a id="Users" name="Users" />
|
|
<h3>Users and User Roles</h3>
|
|
|
|
<p>After an organization has been defined, users associated with the organization can be entered. User information can be entered by using either:</p>
|
|
<ul>
|
|
<li>The User page (accessible by clicking "Users" on the top menu bar or by clicking "Manage Users" on the system administrator's home page). </li>
|
|
<li>The registration user (accessible by clicking "New Location/User Wizard" on the system administrator's home page—<a href="epriman4.htm#Registration">Section 4.4</a>). </li>
|
|
</ul>
|
|
|
|
<a id="fig8" name="fig8" />
|
|
<p>The system administrator can display a list of all users that have been entered on the User Page (<a href="eprimf8.htm">Figure 8</a>, 27 KB). </p>
|
|
|
|
<p>The majority of the attributes of each user are self-explanatory, including name, E-mail address, telephone, fax, mailing address, city, State, and ZIP code. Attributes of particular note are: </p>
|
|
|
|
<ul>
|
|
<li>Username. The username can be up to 20 characters in length. </li>
|
|
<li>Password. The password can be up to 16 characters in length. Note that the password is stored in an encrypted form in the SQL database. If a user forgets their password, the system administrator must create a new password for them, tell them (by phone or E-mail) what the new password is, and ask them to log in to the system and change their password. </li>
|
|
<li>Organization. When logged in as the system administrator, the drop down list contains all the organizations entered on the Organization Page (<a href="epriman3.htm#Setup">Section 3.1</a>); when logged in as an organization's data manager, the drop down list only contains the data manager's organization.</li>
|
|
<li>Input Role. The input role controls the user's access to EPRI's data entry functions. There are four input roles:
|
|
<ul>
|
|
<li><strong>Administrator.</strong> The system administrator has access to all data entry functions—i.e., they can add, edit, and delete resources, resource types, location types, locations, organizations, users, and inventory levels. </li>
|
|
<li><strong>Data Manager.</strong> Each organization has one data manager. The data manager can add, edit, and delete locations and users associated with their organization, as well as inventory data for any of the organization's locations. </li>
|
|
<li><strong>Data Enterer.</strong> Data entry staff for an organization can only enter inventory data for locations associated with their organization. </li>
|
|
<li><strong>None.</strong> A user—particular persons who will only be running reports—can be denied access to all data entry functions.</li>
|
|
</ul> </li>
|
|
<li>Output Role. The output role controls the user's access to reports. There are five output roles—Levels 1 thru 4 and 'None.' A Level 4 output role means that the user has access only to those reports that the system administrator has defined as Level 4 reports; a Level 3 output role provides access to Level 3 and 4 reports, and so on. In our pilot test, only the system administrator had Level 1 access. Procedures for controlling access to reports are discussed in <a href="epriman6.htm">Section 6</a>. </li>
|
|
</ul>
|
|
|
|
<h4>Home Page</h4>
|
|
<p>After a user logs into the system, the links on the Home Page reflect the user's access privileges. </p>
|
|
|
|
<a id="fig9" name="fig9" />
|
|
<p>The system administrator's home page contains links to all system features (<a href="eprimf9.htm">Figure 9</a>, 18 KB).</p>
|
|
|
|
<a id="fig10" name="fig10" />
|
|
<p>By contrast, the home page of an organization's data manager has links to only the User, Location, and Reports Pages (<a href="eprimf10.htm">Figure 10</a>, 18 KB).</p>
|
|
|
|
<a id="fig11" name="fig11" />
|
|
<p>Finally, a Data entry person's home page only has a link to the Location and Help page (<a href="eprimf11.htm">Figure 11</a>, 17 KB).</p>
|
|
|
|
<h4>Location Page</h4>
|
|
<p>The contents of the Location Page varies accounting to the user's Input Role. </p>
|
|
|
|
<a id="fig12" name="fig12" />
|
|
<p>The system administrator's Location Page shows all locations (across all the organizations) entered in EPRI. They can also add a new location for any organization, edit and delete information on any location, and add, edit, or delete inventory information for any locations (<a href="eprimf12.htm">Figure 12</a>, 31 KB).</p>
|
|
|
|
<a id="fig13" name="fig13" />
|
|
<p>The data manager's Location Page shows only locations associated with their organization (<a href="eprimf13.htm">Figure 13</a>, 29 KB).</p>
|
|
|
|
<a id="fig14" name="fig14" />
|
|
<p>The data enterer's Location Page also shows only locations associated with their organization, but, unlike the data manager and system administrator, data enterer cannot add new locations or delete, edit or send E-mail to existing locations (<a href="eprimf14.htm">Figure 14</a>, 23 KB).</p>
|
|
|
|
<p class="size2"><a href="index.html#contents">Return to Contents</a></p>
|
|
|
|
<a id="Registration" name="Registration" />
|
|
<h3>Registration Wizard</h3>
|
|
<p>New users can be added to EPRI in two different ways. As explained earlier in Section 4, the system administrator can directly enter new organizations, locations, and users on their respective Web pages.</p>
|
|
|
|
<p>In addition, a "registration wizard" was developed to streamline registration of (what was for us) the most common configuration—an organization that has a single location and a single user. Thus, rather than separately displaying and entering data in the Organization Page, then the Location Page, and then the User Page, the wizard guides the user through this process. It should be emphasized that the wizard is intended to handle only the special case of a single organization, single location, and single user. If an organization has other locations and users, this information will have to be entered outside of the wizard. </p>
|
|
|
|
<p>The wizard has three steps:</p>
|
|
<a id="fig15" name="fig15" />
|
|
<ol><li>The first screen asks for location information (<a href="eprimf15.htm">Figure 15</a>, 20 KB).</li>
|
|
<li><a id="fig16" name="fig16" />The second screen asks for organization information. The administrator can either select an existing organization or create a new one (<a href="eprimf16.htm">Figure 16</a>, 20 KB). </li>
|
|
<li><a id="fig17" name="fig17" />Finally, user information is provided (<a href="eprimf17.htm">Figure 17</a>, 19 KB). </li>
|
|
</ol>
|
|
|
|
<p class="size2"><a href="index.html#contents">Return to Contents</a><br />
|
|
<a href="epriman5.htm">Proceed to Next Section</a></p>
|
|
<div class="footnote">
|
|
<p> The information on this page is archived and provided for reference purposes only.</p></div>
|
|
<p> </p>
|
|
</div>
|
|
</td>
|
|
</tr>
|
|
</table>
|
|
<!-- End of Center Content section -->
|
|
</td>
|
|
</tr>
|
|
</table>
|
|
</div>
|
|
<!-- End of Content Body -->
|
|
<!-- Footer graphic 1.2-->
|
|
<table cellspacing="0" cellpadding="0" border="0" width="100%">
|
|
<tr>
|
|
<td width="125" background="/images/bottom_ahrq_bkg.jpg"><img src="/images/bottom_ahrq_1.jpg" width="125" alt="AHRQ" /></td>
|
|
<td width="100%" background="/images/bottom_ahrq_bkg.jpg" ><img src="/images/bottom_ahrq_bkg.jpg" width="10" height="34" alt="" /></td>
|
|
|
|
<td width="310" background="/images/bottom_ahrq_bkg.jpg"><img src="/images/bottom_ahrq_2.gif" alt="Advancing Excellence in Health Care" width="310" height="34" /></td>
|
|
</tr>
|
|
</table>
|
|
<!-- Footer links section -->
|
|
<div id="banner_Footer2"><p> <a href="https://www.ahrq.gov/">AHRQ Home</a> | <a href="https://info.ahrq.gov" class="footer_navlink">Questions?</a> | <a href="https://www.ahrq.gov/contact/index.html" class="footer_navlink">Contact AHRQ</a> | <a href="https://www.ahrq.gov/sitemap.html" class="footer_navlink">Site Map</a> | <a href="https://www.ahrq.gov/policy/electronic/accessibility/index.html" class="footer_navlink">Accessibility</a> | <a href="https://www.ahrq.gov/policy/electronic/privacy/index.html" class="footer_navlink">Privacy
|
|
Policy</a> | <a href="https://www.ahrq.gov/policy/foia/index.html" class="footer_navlink">Freedom of Information Act</a> | <a href="https://www.ahrq.gov/policy/electronic/disclaimers/index.html" class="footer_navlink">Disclaimers</a> | <a href="http://www.hhs.gov/open/recordsandreports/plainwritingact/index.html" class="footer_navlink">Plain Writing Act</a> <br />
|
|
|
|
<a href="http://www.hhs.gov" class="footer_navlink">U.S. Department of Health & Human Services</a> | <a href="http://www.whitehouse.gov" class="footer_navlink">The White House</a> | <a href="http://www.usa.gov" class="footer_navlink">USA.gov: The U.S. Government's Official Web Portal</a></p>
|
|
</div>
|
|
<div id="banner_Footeraddress"><p>Agency for Healthcare Research and Quality <img src="/images/bottom_dot.gif" alt="" /> 5600 Fishers Lane Rockville, MD 20857 <img src="/images/bottom_dot.gif" alt="" /> Telephone: (301) 427-1364</p></div>
|
|
|
|
<!-- End of Footer links section -->
|
|
</body>
|
|
</html> |