@Michelle Troxell Attaching a single Document Type to different attachment levels is very much possible - in Epic, and that's the core of Crystal's question. Keep in mind that we're all here talking about Crystal's situation.
In our situation, we have a handful of Document Types that are configured differently in the Registration Document Table than they are in the interface, so depending on the ingestion method the document may be attached to either the patient or the encounter in Epic. In OnBase, of course, the document is attached to a patient/encounter as configured in the Chart Context Document Types in Config. This has been annoying and caused problems with missing keyword values and some documents not moving after a Contact Move in Epic. I think it'll take a Hyland resource to jump in with an official recommendation, but from my own experience, my personal recommendation is to try and keep every Document Type attaching to a single attachment level and split them out as necessary. For example, we have a document type called "Notice of Non-Covered Service" and another called "Notice of Non-Covered Service Encounter" just to account for different registration workflows.
Unfortunately, we've chosen not to move forward with WBPT and I'm not finding any documentation from Epic or Hyland that specifies whether there should be a 1:1 relationship between Doc Types and Attachment Levels for WBPT to work.
