Electronic Health Information (EHI) Export

Documentation Ehnote EHI Export

Ehnote Inc.

  1. PHI (Protected Health Information) can be exported from EHR (Electronic Health Record) systems, enabling efficient information sharing between healthcare providers while protecting patient privacy and security. Ehnote provides export file users with access to export format documentation so they may handle EHI after it has been exported using Ehnote

    The user will gain an understanding of the files that are produced by the PHI Export by using this documentation guide. It will provide further insight to ensure that this vast amount of information is used effectively, as well as instructions on how to read the files and comprehend the meaning of fields and connections.

  2. An export will include a single patient, depending on the specifications. All the files will be downloaded individually once the export and download button is clicked

    A number of files including patient Investigations, Surgery consents, Referrals, Billings and Authorization files and Case history can be found in this collection.

    • These files will be exported as a PDF file. The naming structure will be "CaseSheet" – represents it as a case sheet + BranchId - _#### (clinic’s branch number) + Patientid – P#### + Appointmentdate - A#### (Date of the appointment) + Filetype – (.PDF)

      • #### - BranchId
      • P#### - PatientId
      • A#### - Appointment date
      • (.PDF) – File type

      For example, CaseSheet_731P518612_A2023-12-08.pdf (731- Branch Id, 518612 – PatientId, 2023-12-08 – Appointment date, .pdf – File type)

    • These files will be exported in their native image format. Generally, but not limited to PNG, and JPEG.

      The naming structure will be Name####_P###_2023####_ .png. Where ### is the patient name number, P### will be patient Id, 2023#### is the date of file upload and .png will be file name

      For example, Alice_P2546_2023-01-08.PNG (Alice – Patient name, P2546 – Patient Id, 2023-01-08 – Appointment date, .png – File type).

  3. Understanding how these files fit together to create a comprehensive picture for the resulting patient or patients) may be the most crucial aspect of using this collection of files. In summary, each file pertaining to a single patient will be shortened using the same P###_ patientidentifier, as previously mentioned.

    Taking a step down, and focusing on the PNG, JPEG and PDF files, it’s broken up into following categories. Investigations, Surgery consents, Referrals, Case sheets and Authorization file types.

    • These are all the .JPEG and .PNG files where if the file type is “Surgery”, “Investigation”, “Referrals” or “Authorization”. One may refer to their special identification as a surgery or investigation. The Patient Identifier, where the extension "P"### will be used, is the crucial field.

    • Patient case sheets are saved in .PDF formats, where patients entire clinical history for a particular appointment will be downloaded, The key field is the Patient Identifier where the extension “P”### will be followed with the Appointment date########

  4. There is no "one size fits all" set of fields in the software because of the extensive customization that is possible. That being said, each primary PDF file that is exported will have a companion file.PNG as well.JPEG files were downloaded

    These files are basic image files with .JPEG, .PNG extension. In PDF’s each row will have a field names that related to the case history along with the clinical data represented For example, as part of the *_Patient.PDF:

    DATA: Name of the clinic, patient demographics, Chief complaints, Review of systems, Assessments, Medications and other clinical data part of the appointment

      • "Ehnote Inc." may be referred to as "we," "our," or "us" in this Agreementand designates Ehnote Inc
      • "Healthcare Provider" or "our clients" denotes Ehnote Inc. licensed and active users.
      • "You" refers to any individual working on your behalf, as well as any workers or contractors employed by the company, as well as any other entity that views, uses, or obtains data through the API.
      • There are no extra costs associated with setting up, configuring, or accessing the API when using the Ehnote PHI Export as mentioned above.
      • If the export size exceeds the contracted available size of your instance, there may be fees for clients hosted on our cloud instances for larger data storage requirements or IT support. Costs and Limitations are publicly available.

    • When using Ehnote, you must abide by all applicable laws, rules, and third-party rights. This cannot be utilized for illicit purposes or in a way that infringes upon the rights of others. It can't go against any other Ehnote or our clients' terms of service.

      It is your responsibility to make sure that all parties representing your company, including contractors, affiliates, and employees, abide by the laws, rules, and these Terms. You also agree not to intentionally encourage violations of the law.

      • Users may have their access to Ehnote or the data owner (such as the medical organization) restricted or removed at any time. Additional grounds for removal consist of, but are not restricted to:
      • Any protected connectivity content from the product may be shared or sublicensed for use by an unregistered application.
      • Execute a task with the intention of exposing the interface to any malware, Trojan horses, worms, viruses, or other destructive objects.
      • Defame, abuse, harass, stalk, or threaten others.
      • Interfere with or disrupt the APIs or the servers or networks providing the APIs.
      • Reverse engineer or make an attempt to extract the source code from any associated software or API, unless the applicable law expressly prohibits this restriction.
      • Encourage illegal internet gaming or bothersome commercials or messaging.
      • Eliminate, conceal, or modify the Ehnote terms of service or associated notifications.
      • Collecting data outside the agree upon context of usage.
      • Assigned credentials must be used solely for their intended purposes and within assignedaccess scopes.

    • A commercially reasonable effort must be made to safeguard any information, including personally identifiable information ("PII"), that your designee accesses. As mandated by law, any unauthorized use or access must be reported right away.

      a. Data exported is owned by the “data owner” not Ehnote.

    • Without our prior written consent, you are not permitted to make any statements that suggest a partnership, sponsorship, or endorsement by Ehnote. The trademarks belong exclusively to Ehnote. Use of the Ehnote name, logo, and trademarks must follow our published policies.

      • As allowed by law, Ehnote and our clients will not be held liable for specific losses or damages. The amount you paid us or our clients to use the relevant product is the maximum amount we will be liable for under the Terms.
      • When using the APIs for improper purposes, breaking the terms of service, or using content that interferes with any function, you, as a business, agree to defend, indemnify, and hold harmless Ehnote and our clients, directors, officers, employees, and users against certain liabilities, damages, losses, costs, fees, and expenses related to third-party legal proceedings.
      • The function meets the requirements of the Electronic Health Information export criterion §170.315(b)(10) in the 2015 Edition Cures Update.
      • If you have any questions about Ehnote PHI Export related to development, please contact (Note: Questions concerning the data itself should be addressed to the original data owner/originating office). Ehnote is unable to respond to the following questions):