In OnBase, there is a doc type group and a doc type, that’s it. You cannot create a hierarchy of types like in DCTM. This has many ramifications good and bad. This limits the potential for complexity, which plagues some DCTM object type designs. However, you can’t use doc types as an organizing factor for more than two levels of categorization in OnBase, which is annoying in medical records when you have hundreds of doc types and one doc type group called, “medical records”. Picture constantly having to scroll through hundreds of doc types for each search, retrieval, scan queue, etc. It’s not productive.
Change Management: A huge plus of OnBase is that you can version a doctype. This allows you to add/delete/change metadata and move on with the modified doc type definition, leaving the previous version with the old content. This is huge when you consider records and auditing. In DCTM, you would have to modify the existing doc type which would change all the previous content, or create a new doc type and migrate the old content. A real hassle if you've ever done it.
Part 2 looks at relations in Document and Onbase and compares some of them.