DAPS 101

From Docs

Jump to: navigation, search

Document Activity Profile: A set of rules that defines how documents behave (are processed) in the system
Every document in the system is associated to at least 1 DAP. Documents can be associated to more than 1 DAP. DAPS can be associated at the following levels:

• Global level

• Specialty level

• Category level

• Document level (Child, Normal, Image, etc.)

These settings control the behavior of the wizard.

Parent Document – Controls the basic form of the document (May be created/managed by both DM and client Admin users, except for VA)

Progress Note – Controls the form and content of the progress note associated with the document (May be created/managed by both DM and client Admin users)

Process – Allows greater control over how the wizard progresses from section to section (Only DEV can create/manage a process)

Presentation Mode – Controls what wizard components actually display out of all the possibilities (Only DEV can create a presentation mode. “Details” button allows DM user to make edits.)

Image Editor Template – Controls what additional components are added to a raw image (May be created/managed by both DM and client Admin users)

Controls what the Final View form for the document looks like and how the system behaves if the user leaves the final View form open for extended periods of time.

The attributes available here are all manageable by the client user. If some options are grayed out, they have been disabled via “global settings” in the database (on a client- by-client basis)

Controls the text that appears on the Reminder Screen. Completely user-editable.

Associates a document to one or more DAPs.

Commonly observed rules:

• There is 1 DAP distributed automatically with the iMedConsent application. It is basically a “default” DAP for non-consent documents.

DAPS for non-consent documents usually defined at the “highest”, i.e., global level.

DAPS for consent documents are usually NOT defined at the Specialty level, but normally at the Category level, and less frequently, at the document level.

How this works:
From the specific to the general.
When a document is launched, the program begins looking for the most specific DAP. It begins looking in this order for:

  1. The DAP associated specifically to the document.
  2. The DAP associated to the category the document is in.
  3. The DAP associated to the Specialty the document is in.
  4. In lieu of any of the above, the system-provided “default” DAP.

If a DAP is found at any point in this progression, the search will stop. If one DAP was found at the level at which the search stopped, it will use that DAP. If more than one DAP is found at this level, then the DAP selection screen will appear, and all possible DAPs will be shown for selection.


This information is only applicable for deployments requiring an interface to an electronic patient records system (e.g., VA). Controls how the receiving system handles the progress notes and images created by iMEdConsent.

This tab is only visible to DM users and relates to the communication between the document server and the receiving imaging system

Personal tools