{"aaData": [["DICTATION", "authorization\n", "document\n", "", "DICTATE\n", "BE DICTATED\n", "", "", "", ""], ["UNSIGNED NOTIFICATION", "subscription\n", "document\n", "", "", "", "", "", "", ""], ["UNCOSIGNED NOTIFICATION", "subscription\n", "document\n", "", "", "", "", "", "", ""], ["PRINT RECORD", "authorization\n", "document\n", "", "PRINT\n", "BE PRINTED\n", "", "", "\n- \n\n
\n", ""], ["DELETE RECORD", "authorization\n", "document\n", "", "DELETE\n", "BE DELETED\n", "", "", "", ""], ["COPY RECORD", "authorization\n", "document\n", "", "COPY\n", "BE COPIED\n", "", "", "", "\nThis describes the copy action, which allows the user to copy a progress\nnote (or other document) from one patient or encounter to another.\n
\n\n"], ["SEND BACK", "authorization\n", "document\n", "", "SEND BACK\n", "BE SENT BACK\n", "", "", "", "\nThis action involves sending back a document to transcription for\ncorrection (and possibly redictation). It removes documents which require\nrelease from view, except by the originator or a transcriptionist.\n
\n\n"], ["AMENDMENT", "authorization\n", "document\n", "", "AMEND\n", "BE AMENDED\n", "", "", "", "\nThis involves the Privacy Act Amendment of a document by authorized\nindividuals AFTER Electronic Signature.\n
\n\n"], ["MAKE ADDENDUM", "authorization\n", "document\n", "", "ADDEND\n", "BE ADDENDED\n", "", "", "", "\nAddenda may be added to documents for the purposes of clarification,\naugmenting, or disclaming existing information. Addenda may be thought of\nas extensions of their parent documents, and inherit their properties from\nthem (i.e., an addendum to a discharge summary is treated like a discharge\nsummary, while an addendum to a progress note is treated like a progress\nnote, etc.).\n
\n\n"], ["ENTRY", "authorization\n", "document\n", "", "ENTER\n", "BE ENTERED\n", "", "", "\n- \n\n
\n", ""], ["IDENTIFY SIGNERS", "authorization\n", "document\n", "", "IDENTIFY SIGNERS FOR\n", "HAVE SIGNERS IDENTIFIED\n", "", "", "", "\nThis action allows the identification of users whose concurrence is\nexpected, but NOT REQUIRED. It may be used by the author of a note to\ncall a given document to another user's (e.g., teammate's) attention. An\nexample might be a Resident or Fellow who wishes for a Staff Physician's\nconcurrence on a complex note or consult. The recipient of the alert for\nconcurrence signature may add an addendum or sign the document, but may\nnot generally edit the document itself. His signature in this case does\nNOT complete the document, but merely indicates concurrence.\n
\n\n"], ["REASSIGN", "authorization\n", "document\n", "", "REASSIGN\n", "BE REASSIGNED\n", "", "", "", "\nReassignment of records involves the correction of Patient, Visit, or\nSignatory information, and may typically be accomplished by the author or\nMIS prior to signature, or by the CHIEF, MIS following signature.\n
\n\n"], ["CHANGE TITLE", "authorization\n", "document\n", "", "CHANGE THE TITLE OF\n", "HAVE ITS TITLE CHANGED\n", "", "", "", "\nThis describes the action by which a title may be changed at appropriate\ntimes during the life of a document (e.g., conversion of a posting to\nanother title, or to a progress note of a given title, etc.).\n
\n\n"], ["LINK WITH REQUEST", "authorization\n", "document\n", "", "LINK\n", "BE LINKED with a request\n", "with a request\n", "", "", "\nThis action involves the linking (or re-linking) of a result with a\nrequest in another application (e.g., a PULMONARY CONSULT with its\ncorresponding request).\n
\n\n"], ["ATTACH TO ID NOTE", "authorization\n", "document\n", "", "ATTACH\n", "BE ATTACHED to an ID note\n", "to an interdisciplinary note\n", "Rule applies to individual ID CHILD entries\n", "", "\nThis action applies to interdisciplinary CHILD notes. Rules involving\nthis action determine whether or not a particular child note can be\nattached to ID parents, and who can do the attaching.\n \nTwo rules are required if a document CHILD is to be attached to a\ndocument PARENT. The first rule uses this action, ATTACH TO ID NOTE, and\npermits the particular CHILD to become an entry under an ID parent. The\nsecond rule uses action ATTACH ID ENTRY, and permits the particular PARENT\nto receive ID children.\n
\n\n"], ["ATTACH ID ENTRY", "authorization\n", "document\n", "", "ATTACH AN INTERDISCIPLINARY ENTRY TO\n", "BE GIVEN AN ID ATTACHMENT\n", "", "Rule applies to interdisciplinary PARENT notes\n", "", "\nThis action applies to interdisciplinary PARENT notes. Rules involving\nthis action determine whether or not a particular parent note can receive\nID children, and who can do the attaching.\n \nTwo rules are required if a document CHILD is to be attached to a\ndocument PARENT. The first rule uses action ATTACH TO ID NOTE, and\npermits the particular CHILD to become an entry under an ID parent. The\nsecond rule uses this action, ATTACH ID ENTRY, and permits the particular\nPARENT to receive ID children.\n
\n\n"], ["LINK TO FLAG", "authorization\n", "document\n", "", "LINK\n", "BE LINKED to a PRF flag\n", "to a PRF flag\n", "", "", "\nThis action involves linking (or re-linking) an EXISTING Patient Record \nfor documents which already exist. Such documents may have been created\nbefore PRF Phase II introduced links and have NO links, or they may\nrequire re-linking to the correct Assignment History Action for the\ncorrect patient and flag assignment.\nFlag (PRF) document to a Patient Record Flag.\n \n(More accurately, a PRF document is linked to an Assignment History Action\nfor a given patient, a given flag, and a given flag assignment.)\n \nUsers authorized to create NEW PRF documents are automatically authorized \n(in fact, REQUIRED) to link the new documents when creating them. Explicit\nauthorization for (re)-linking a PRF document to a flag is required only\n
\n\n"], ["EDIT COSIGNER", "", "", "", "EDIT THE COSIGNER OF\n", "HAVE ITS COSIGNER EDITED\n", "", "", "", "\nThis USR action only applies to editing the Expected Cosigner of\ndocuments. Use USR action EDIT RECORD for more general edit authorization.\n \nThis action is intended for Clinical Coordinators. Rules for this\naction are recommended in the patch description for patch USR*1*30.\n
\n\n"], ["VERIFICATION", "authorization\n", "document\n", "", "VERIFY\n", "BE VERIFIED\n", "", "", "\n- \n\n
\n", ""], ["SIGNATURE", "authorization\n", "document\n", "", "SIGN\n", "BE SIGNED\n", "", "", "\n- \n\n
\n", ""], ["COSIGNATURE", "authorization\n", "document\n", "", "COSIGN\n", "BE COSIGNED\n", "", "", "\n- \n\n
\n", "\nThis event occurs when the second-line signature is obtained for a document.\n\n
\n\n"], ["VIEW", "authorization\n", "document\n", "", "VIEW\n", "BE VIEWED\n", "", "", "", ""], ["RELEASE FROM TRANSCRIPTION", "authorization\n", "document\n", "", "RELEASE\n", "BE RELEASED FROM TRANSCRIPTION\n", "FROM TRANSCRIPTION\n", "", "\n- \n\n
\n", ""], ["EDIT RECORD", "authorization\n", "document\n", "", "EDIT\n", "BE EDITED\n", "", "", "\n- \n\n
\n", "\n \nUsers authorized to perform this event may edit the text of associated\ndocuments.\n
\n\n"]]}