Difference between revisions of "Co-sign their notes"
Jump to navigation
Jump to search
(2 intermediate revisions by one other user not shown) | |||
Line 5: | Line 5: | ||
*PA's finalization authority must be lower than the document type finalization authority. | *PA's finalization authority must be lower than the document type finalization authority. | ||
− | * | + | *In the [[Document Type]] dictionary, on the document types a PA may use, place a check mark on "Prompt User to Route for Further Signature" to be used for PA's. |
Workflow: | Workflow: | ||
− | *PA creates note, signs note as author | + | *PA creates note, signs note as author. |
*This forces a task window to appear for PA to send a "co-sign" note task to provider when they sign initially. This allows the flexibility for those PA's who may alternate which physician they have co-sign their notes. | *This forces a task window to appear for PA to send a "co-sign" note task to provider when they sign initially. This allows the flexibility for those PA's who may alternate which physician they have co-sign their notes. |
Latest revision as of 20:08, 26 November 2012
How do I set up Allscripts for physician assistants who require a supervising physician to co-sign their notes?
Set Up:
- PA's finalization authority must be lower than the document type finalization authority.
- In the Document Type dictionary, on the document types a PA may use, place a check mark on "Prompt User to Route for Further Signature" to be used for PA's.
Workflow:
- PA creates note, signs note as author.
- This forces a task window to appear for PA to send a "co-sign" note task to provider when they sign initially. This allows the flexibility for those PA's who may alternate which physician they have co-sign their notes.