Manually Uploading Attachments to HCHB

Manually Uploading Attachments to HCHB

Sometimes, an attachment needs to be uploaded without using Forcura. Follow the below steps to learn how to manually upload an attachment to a patient's chart in R2.

Manually Attaching

  1. Find the patient under Clinical Input, highlight them so the buttons across the bottom light up.
  2. Select Attachments and then either Episode or Patient (explanation below for the difference between those).
  3. Click Import on the Attachment screen that pops up.
  4. Follow the folder path to find your file. Typical path is: This PC > Local Disk C: > User > YourName > then Downloads, Desktop, Documents, wherever you saved the file at.
  5. Select the file then Open
  6. In the dropdowns on the right, select the proper information.
    1. Type - What type of document is it? Orders, Documentation, H&P
    2. Location - This populates for you, but it is where the attachment will be saved
    3. Recipients - If you started with a specific patient, this will populate for that patient
    4. Effective Date Range - Use this for visit notes or consents, indicating date of visit or date consent was signed. For all other attachment types, you will usually leave this as is
    5. Renewal Reminder Pattern - This can be ignored, unless you want a reminder to update that attachment every so many days
  7. Click Apply Settings to Checked Files.
  8. Click Save & Close.
  9. Tada!








Patient Attachments vs Episode Attachments

Patient
      These are going to be items that stick with the patient no matter how long they are on service for, as well as any future new episodes (even cross service lines)
      Items like this will be: Referral Packet, Consents Obtained on Paper, Signature Forms, Advanced Directives, etc.

Episode
      These are specific to only that episode. They don't need to stick with the patient in future episodes.
      Items like this will be: Signed Orders, Physician Order, ROC Packet, Care Coordination, Signed CTI, HOS Election Addendum, etc.