1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30
Office of Administrative Hearings 1400 West Washington, Suite 101
Phoenix, Arizona 85007 (602) 542-9826 IN THE OFFICE OF ADMINISTRATIVE HEARINGS
IN THE MATTER OF:
PROFESSIONAL MEDICAL TRANSPORT, INC. dba
PMT AMBULANCE
Applicant.
No. 11A-EMS-0157-DHS
CASE MANAGEMENT ORDER No. 1 Modifying Document Service and Filing Requirements to Require Electronic Filing
1. ELECTRONIC FILING IS REQUIRED
Given the number of interested persons and potential interveners, to reduce the expense and complexity of providing service for all pleadings and other filings:
A. EXCEPT AS OTHERWISE REQUIRED FOR EXHIBITS (SEE ¶2 BELOW), paper filing will not be permitted; electronic filing will be required through the following webpage: https://portal.azoah.com/oedf/ . A password for submission will be supplied to each party and interested person listed on this order. (The password will be supplied by a separate email that will not be made public.) Technical questions regarding the use of the webpage should be directed to
webmaster.webmaster@azoah.com;
B. Upon the filing of a document, an e-mail will be automatically generated and sent to all parties, interested persons, and counsel. Receipt of the e-mail is verification of submission to the Office of Administrative Hearings (“OAH”), and all other parties and interested persons.
C. Electronic filing will constitute valid service and no service to the other parties or interested persons will be required. See A.R.S. § 41-1092.04; Arizona Administrative Code R2-19-102;
D. All electronic filings must be in PDF format. Files that are not so configured will be rejected;
E. All filings must be set to limit page sizes to 8 ½ x 11; files that are not so configured will be rejected;
F. The electronic case file, universally accessible without password, is posted at
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30
2. EXHIBITS MUST BE SUBMITTED ON CD OR DVD AND IN PAPER FORM
NOTWITHSTANDING ¶ 1, IT IS ORDERED that exhibits must be filed in paper
form, contemporaneously with electronic copies on CD or DVD. Individual service to the other parties and interested persons is not required. The OAH webmaster will post the electronic exhibits on the electronic docket, which will generate an email to each party and interested persons. The paper copies of the exhibits will constitute the exhibits of record for purposes of any appeal.
IT IS FURTHER ORDERED setting the following standards for filing electronic and hard copy exhibits:
A. Exhibits are to be marked as follows: Each known party or interested person has been assigned a designator (in bold on themailing list below). Exhibits must be marked sequentially with the designator, followed by the number; e.g. PMT-1, PMT-2, etc.
B. Electronic exhibits must be submitted on a CD or DVD. Such CD or DVD must be accompanied by a statement that the electronic exhibits are true and accurate copies of the hard copy exhibits.
C. Electronic exhibits must be in one of the following formats:
1) Portable Document Format (.pdf) 2) Graphic types: JPG, GIF, or PNG.
D. The electronic exhibits must be indexed in an html file designated “index” with active links to each exhibit. Because the contents of the CD/DVD will be transferred to the Office of Administrative Hearings’ server for use at hearing, links must be relative, not absolute. See Technical Bulletin 1, attached. Technical questions may be referred to webmaster.webmaster@azoah.com .
E. Each electronic exhibit must be referenced in the index in the following manner:
1) The exhibit designation as set forth, above (e.g. PMT-1); and 2) Followed by a descriptive exhibit name. “Application”
Example: PMT-1 (active link) Application (descriptive name)
3. ORDERS TO OAH WEBMASTER
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30
prior to the issuance of this Order to be reflected in the electronic docket.
IT IS FURTHER ORDERED that the OAH Webmaster is directed to make any required technical modifications to the electronic docket, with such technical modifications to be noted by the Webmaster on the electronic docket by appropriate means.
IT IS FURTHER ORDERED that the OAH Webmaster is directed to post technical bulletins as may be considered useful.
Done this day, January 27, 2011.
/s/ Thomas Shedden
Thomas Shedden
Administrative Law Judge
Copy e-mailed this 27th day of January, 2011 to:
Will Humble, Director
Arizona Department of Health Services
Jan.Escoto@azdhs.gov
Kevin Ray (DHS)
Office of the Attorney General
Counsel for Arizona Department of Health Services
kevin.ray@azag.gov
Patrick McGroder (PMT)
Gallagher & Kennedy
Counsel for Applicant PMT Ambulance
pjm@gknet.com
Lawrence J. Rosenfeld, Esq. (SWA)
Greenberg Traurig, LLP
Counsel for Intervenor Southwest Ambulance
rosenfeldl@gtlaw.com
Brian Tobin (DMFD)
Daisy Mountain Fire District
brian.tobin@dmfd.org
David Birchfield (GBRA)
Gila Bend Rescue/Ambulance jcarpenter@gilabendaz.org
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30
John Valentine (RMI)
River Medical, Inc.
John.Valentine@emsc.net
Steve Holt (TBFD)
Tonto Basin Fire District
tbfdchief@netscape.net Jim Roeder (PMT) PMT Ambulance jroeder@amlifestar.com jroeder@pmtambulance.com Paul S. Wilson (SLFD)
Sun Lakes Fire District
pwilson@slfd.org
Lonnie Guthrie (AJO)
Ajo Ambulance, Inc.
lguthrie@tabletoptelephone.com
Thomas A. Birch (BCFD)
Black Canyon Fire District
dba Black Canyon Fire Department
chief@bcvfd.org
Cheryl A. Smith (LLASI)
Life Line Ambulance Service, Inc.
CSMITH@LIFELINEAZ.COM
Scott Benbow (BVVRU)
Buckeye Valley Rural Volunteer Fire District dba Buckeye Valley Volunteer Rescue Unit
markalexander@cox.net
Charlie M. Smith (CSA)
LifeStar, LLC, dba Canyon State Ambulance
csmith@lifestar.us ginorio@starwest.us
Harry Eth (DHS)
ADHS/Bureau of Emergency Medical Services Certificate of Necessity and Rates Section
ethh@azdhs.gov
Charlie M. Smith (AA)
AMERICAN AMBULANCE
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 ginorio@starwest.us Ray Temple (PFD)
City of Phoenix dba Phoenix Fire Department
ray.c.temple@phoenix.gov
Roy Ryals, Director of EMS (SWA)
Southwest Ambulance (Maricopa)
Southwest Ambulance of Casa Grande, Inc. Southwest Ambulance and Rescue of Arizona Rural/Metro Corp. (Maricopa)
Rural/Metro Corp. (Yuma)
rryals@swambulance.com
Robert Biscoe (FDSC)
Fire District of Sun City West dba Fire District of Sun City West Ambulance
rbiscoe@scwfire.org
By:
autogenerated and posted to https://portal.azoah.com/oedf/documents/11A-EMS-0157-DHS/index.html
Technical Bulletin 1: Relative Links
Overview: All submitted exhibits must be indexed in html and all targets in the index must be RELATIVE links. This technical bulletin addresses the difference between relative links and absolute links for the purpose of creating an index when submitting exhibits:
A. An absolute link is a link whose target points to some location external to the medium being submitted.
Example: href=”http://www.azwater.gov/dwr/Content/Find_by_Category/Laws _and_Rules/ADWR%20Administrative%20Docket%20and%20Exhi bits/ADWR%2083.pdf” The text, http://www.azwater.gov/dwr/Content/Find_by_Category/Laws_and_ Rules/ADWR%20Administrative%20Docket%20and%20Exhibits/
points to an external location, in this case, a website.
The link can be converted to a relative link by stripping out the language, leaving the following target:
href=”ADWR%2083.pdf”
B. A relative link is a link that points only to location within the submitted medium.
Examples:
href=”Exhibit1.pdf”
In this example, the target simply points to a file found on the medium, in this case, named, Exhibit1.
href=”Exhibits/Exhibit 1.pdf”
In this example, the target points to a folder found on the medium, in this case, named, Exhibit. This founder contains the file named, Exhibit1.
Notes:
NOTE 1: A target must never begin with a “/” as that indicates the root drive of the device opening the medium.
Example:
href=”/Exhibit1.pdf”
In this example, the target points to the root of the computer opening the medium. The link will fail.
NOTE 2: A target must never begin with a drive letter of any sort as that may point to a directory on the party’s network, or absolutely to the medium submitted. In either case the index and associated documents cannot be transferred to OAH servers as required.
Example:
href=”u:/Exhibit1.pdf”
In this example, the text, u:/, may point to the party’s network where the files originally resided, or to the medium being produced. The link will fail when the information is transferred.
Note 3: QUICK CHECK: You will know if your medium index contains no relative links if you can put the medium on a device that is not connected either to the internet, or your network, or which does not contains the files targeted. If the index does not function, you index contains absolute links and must be modified. This test will not factor out an absolute link created by a reference to the medium itself. Being careful not to begin a target with any drive letter (e.g. “b:/”) will eliminate this possibility.
Note 4: Editing HTML to strip out absolute links: You can easily strip out references to locations external to the medium by opening the index in notepad and examining a target document. Search and delete any text referencing an external ink. See above.
Note 5: To review a sample electronic index, go to
