topleft topright

User Registration

MDILog registration process:

  1. Register for an MDILog account.
  2. System will verify and send an activation email to you.
  3. Use link in email to request county access.
  4. Once approved, you will receive a confirmation email.
  5. Start using MDILog.

Get on the MDILog Network!

The following form is to be filled out by a user registering for access to MDILog. Once you have filled out this form and verified your account by email you may then request access to a county or administration of that county. If you are registering to use a new county on MDILog, ORA will verify your information and enable your access to the county. If you are a registering for access to a currently administrated county, the admin of the county will need to accept your request.

* (Username)


  1. Parties to Agreement. This "Case Management System User Terms and Conditions" is between Occupational Research and Assessment, Inc., with offices at 124 Elm Street, Big Rapids, MI 49307 ("ORA"), provider of MDILog software ("MDILog" or the "Software") and the User identified on page 1 of this Software Subscription Agreement ("Agreement").
  2. Software Features and Functions. The Software is provided as a service, and is accessed via the Web at (the "Site"). Its features and functions are located at
  3. Creation of User Account. To create the case management portfolio, to upload video, images, text, sound recordings, and other User content ("Content"), and to access some features and services offered by ORA at the Site, User must create an account. User will receive a password and an account designation.
  4. Importance of Content Backup. User is responsible for downloading and backing up copies of all its Content on a regular basis to ensure that it always has access to its own Content. Although ORA has designed the Site to enable uptime of over 98%, ORA relies upon third parties for power, data storage, server access, software maintenance, system troubleshooting, system security, and other technology services. The Site will occasionally be down (and the Content inaccessible) for testing, upgrading, and maintenance.
  5. Account Security. User is responsible for its account, the accuracy of all information uploaded to its account, and all activities occurring in connection with use of the account. Only User authorized representatives (employees and contractors) are shall access the Software or upload Content. User shall keep passwords secure and notify ORA promptly of any suspected breach of security or unauthorized use of its account. User can access its account, review the Information that is stored, and revise or delete that Information. User will need to contact ORA to delete its entire account. User shall ensure it has the legal right to upload the Content to the Software database, and that possession and storage of the Content by ORA (or its subcontracted technical hosts) is lawful and does not violate any state or federal law or violate the rights of any third party.
  6. Super Users. Some Users (such as a governmental jurisdiction) may have two individuals designated as a Super Administrator or "Super User." A Super User is the medicolegal officer (medical examiner or coroner) of the User jurisdiction or their designee. The Super User will have the sole ability to (a) "activate" and "delete" its delegates under the account established with ORA; (b) add secondary counties/parishes; (c) export account Information; (d) customize permission sets; (e) request to add additional autopsy facilities to the account; (f) activate/deactivate account Information exchanges with ORA authorized partners (e.g., AIT, NMS, OPO, EDRS); and (g) be the point of contact for ORA. For more information about Super Users, see
  7. Grant of License. ORA grants User (its employees and contractors) the right to access the Site and use the Software service for User's medicolegal death investigation case management. This authorized access is non-exclusive, limited, personal and nontransferable. User may not authorize others to use the Software or access the Site. User is responsible to ORA for compliance by User contractors with the restrictions in this Agreement.
  8. Trial Period; Acceptance/Rejection; Sole and Exclusive Remedies. User has thirty (30) days to use the Software and determine if the Software meets User's needs. If User does not notify ORA in writing within those thirty (30) days that it is rejecting the Software, then the Software has been ACCEPTED and User is responsible for payment of the subscription fees. If User rejects the Software, this Agreement is terminated; User has no rights to access the Software or stored Content and ORA has no further obligation to User. Content will be deleted in the course of the operation of the Site. The remedies provided in this Section are the sole and exclusive remedies provided to User under this Agreement and are in lieu of all other remedies by contract, by law, and at equity.
  9. AS-IS Warranty. User agrees that the thirty (30) day trial period is adequate to test the Software. ACCORDINGLY, ORA PROVIDES, AND USER ACCEPTS, THE SOFTWARE "AS IS," WITH NO WARRANTIES OF ANY KIND, EITHER EXPRESS OR IMPLIED, AND INCLUDING (WITHOUT LIMITATION) ANY WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. ORA does not warrant that the functions contained in the Software will meet User's specific requirements, the requirements of User's particular industry, will be error-free, or operate without interruption. ORA will use commercially reasonable efforts to correct bugs and maintain the Software.
  10. ORA Rights in Software. ORA retains all rights, including intellectual property rights, in the Software, database and Site, including Software features created by ORA at the request of users. User is not granted any right to download the Software, create derivative works, or permit third party access to the Software or Site.
  11. User Content and Data. User retains the rights applicable to its Content and to data generated through User's use of the Software. ORA may use the account information, Content, and information ORA collects from User's use of the Software and the Site (collectively, "Information") (a) to investigate and verify proper conduct at the Site and to monitor the security and integrity of the Site; (b) as required by law and/or in response to service of legal process, such as a court order, summons, subpoena, and the like (ORA shall use reasonable efforts to notify User in advance of any such disclosure); (c) for Information that is not identifiable to an individual or entity, ORA may also use aggregate and anonymous Information to enhance the User experience at the Site, to understand how the Site is used, to communicate with its Users about ORA and the Site, and to analyze, develop, and promote its business; (d) for Information that is identifiable to an individual or entity, ORA may use Information as set forth above in (a) and (b), to implement this Agreement, and to communicate with User about the Software, the Site, and this Agreement; (e) for research purposes, ORA may use non-identifiable case Information to create reports and conduct ongoing research activities that support medicolegal death investigation activities. The authorization set forth in this section is irrevocable, royalty-free, worldwide, and transferable.
  12. Third Party Marks. The Site and the Software may refer to third parties (by name, trademark, links, and the like). ORA makes no representation or warranty regarding such third-party products or services and makes no assertion of a business relationship, affiliation, endorsement, or sponsorship by such third parties unless expressly stated on the Site.
  13. Data Security and Privacy. ORA implements the policies and procedures at
  14. Fees and Payments.
    1. Subscription Basis. Software access is provided on a subscription basis. User shall pay the applicable Software license fees ( see Pricing link), including fees based upon the number of individuals within User who have access to the Software and the data storage needs applicable to User. ORA may adjust fees from time to time, with advance notice to User, and shall not increase prices more than once per year.
    2. Base Services and Additional Services. Certain services are provided as part of the "base" subscription and other features (e.g., automated data transfer from MDILog to organ donation agencies, data export for automated upload into State/County death certificate data) are provided for an additional fee. For Users with Super Users, only a Super User can order such additional features.
    3. Additional Services. User may purchase additional services from ORA at the then-current hourly, per-diem, or per-project rate. User shall pay all travel and living expenses of ORA representatives associated with any meetings, implementation, training, technical support, or other on-site visits. ORA may request that User prepay travel expenses. If ORA investigates any User technical problems with the Software and the problem is found to be caused by operator error, unauthorized modification, tampering, or other cause not inherent in the Software, ORA reserves the right to charge for its services at its then-current technical service rates.
  15. Term. User shall select the term of the Software license (quarterly, yearly). The term shall automatically renew unless either party gives written notice to the other at least ten (10) days prior to end of the then-current term of an intent not to renew, or unless terminated in accordance with this Agreement. If User uses a credit card for payment of its Software license fee, it hereby authorizes ORA to charge such card for each term of use.
  17. Integrity of the Site. User shall not take any action to interfere with the operation of the Software or the Site, to attempt to copy its underlying technology, to upload other computer programs, or copy Content other than User Content. User agrees not to use any automated software (crawlers, robots, bots, spiders, extractors, etc.) at the Site; circumvent, disable or otherwise interfere with security-related features or digital rights management functions at the Site; or hack, reverse engineer, or disable any technology at the Site.
  18. Suspension of Account. In the event of a material breach that is uncured, response to legal process, concern for the integrity of the Site, reasonable suspicion of improper conduct at the Site, or other good faith belief, ORA may suspend or terminate an account, remove or limit access to Content, or limit services to which an account holder has access, and shall use reasonable efforts to provide prior notice to an account holder.
  19. Termination of Services; Termination of Agreement.
    1. Material Breach. Either party may terminate this Agreement if there is a material breach by the other that is not cured within thirty (30) days after receipt of written notice of such breach. Without limitation, failure to pay fees when due, and/or use of the Software inconsistent with this Agreement, are material breaches. Upon termination, User is responsible for ensuring that it has possession of its Content and all data generated by it in connection with the use of the Software. Termination shall not affect the obligation of User to pay any fees and expenses owing as of the date of termination.
    2. User Termination for Convenience. At any time, User may terminate its account, cease using the Software, or delete account information. User may take such actions with or without prior notice to ORA and without any liability to ORA other than payment of Software license fees through the date of termination or the applicable contract period, whichever is longer.
    3. Termination of Access. Upon termination of this Agreement ORA may block access to or delete uploaded Content.
  20. User Responsibility. User acknowledges that its account with ORA and its access to the Software and Site is based upon the truth of the promises, statements, and representations made in this Agreement. User is solely responsible for any costs, expenses, and damages arising from breaches of this Agreement or third party assertions inconsistent with its promises, statements, representations, and warranties. This obligation survives termination of this Agreement. User agrees to use its best efforts to assist ORA in the investigation and resolution of any third party claim or assertion inconsistent with User's obligations under this Agreement, at no charge and promptly upon receipt of notice from ORA of such claim or assertion.
  21. The Site and Software are Located in and Delivered from Big Rapids, Michigan, USA. This Agreement is entered into, performed in, and based in Big Rapids (Mecosta County), Michigan, USA. The Site does not give rise to personal jurisdiction over ORA, either specific or general, in jurisdictions other than Michigan. This Agreement shall be governed by the internal substantive laws of the State of Michigan, without respect to its conflict of laws principles. Any claim or dispute between User and ORA that arise in whole or in part from the Software or this Agreement shall be decided exclusively by a court of competent jurisdiction located in (or having jurisdiction over) Big Rapids, Michigan.
  22. Entire Agreement. This Agreement incorporates by reference all terms appearing at the links identified in this Agreement. The Agreement may be updated and modified by ORA from time to time. Those modifications are incorporated as part of the Agreement. User will be notified of significant modifications when it logs on or accesses its account. If User does not accept the modifications to the Agreement, its sole remedy is to conclude its subscription at the end of the then-current term, or sixty (60) days, whichever is less. Provisions which, by their nature, are intended to survive termination shall continue, by way of example, limitation of liability for damages.
  23. Additional General Terms. No waiver by ORA shall be implied. Any waiver of any term of this Agreement must be in writing and signed by an officer of ORA. If any portion of this Agreement is found to be unenforceable, such portion will be modified to reflect the parties' intent set forth in such portion and only to the extent necessary to make it enforceable. The remaining provisions of this Agreement will remain in full force and effect. ORA may assign, subcontract, delegate, and transfer its rights and obligations under this Agreement to a third party. User may not assign or transfer its account. Each party represents that it has the legal power to enter into this Agreement, and that the person signing this Agreement has the actual authority to bind the User to its terms and conditions. ORA makes no representations that the Site or Software is appropriate or available for use in locations other than the United States. Those who access or use the Site or use the Software from outside the U.S. do so at their own volition and are responsible for compliance with applicable laws.
  24. Notices. ORA may provide User with notices, including those regarding changes to ORA's Software License Agreement, by email, first class mail, or postings to the Site. Notice is deemed given upon the earlier of (a) actual receipt, (b) twenty-four (24) hours after an email is sent, (c) three (3) days after first class mail is deposited with the U.S. Postal Service, or (d) thirty (30) days after a notice is posted to the Site.
  25. Force Majeure. It shall not be a material breach of this Agreement, and neither party shall be liable to the other, if prevented from performing its duties or responsibilities under this Agreement by reason of any fire or other casualty, acts of God, earthquake, floods, explosions, interrupted power supply, sabotage, war, riots, acts of terrorism; inability to procure or a general shortage of labor, equipment, facilities, materials or supplies in the open market; strikes, court orders, laws, regulations, or orders of government or military authorities; or any other cause not within the control of such party whose performance is delayed.

This RSS feed URL is deprecated

This RSS feed URL is deprecated, please update. New URLs can be found in the footers at

10-Year-Old New Canaan Boy Who Died Suddenly Had Flu: Coroner - NBC Connecticut

10-Year-Old New Canaan Boy Who Died Suddenly Had Flu: CoronerNBC ConnecticutA 10-year-old New Canaan boy who died suddenly over the weekend had the flu, according to the medical examiner in Buffalo...

Coroner's office stays busy with more cases in 2017 - Daily Record-News

Coroner's office stays busy with more cases in 2017Daily Record-NewsDue to population size, Kittitas County was required to have a dedicated, elected coroner's office in 2015. Duties previo...
Mdilog by ORA Inc.