{"id":47724,"date":"2022-04-01T20:17:53","date_gmt":"2022-04-01T20:17:53","guid":{"rendered":"https:\/\/assignmenttutors.net\/blog\/plaza-college-ht108-health-care-data-indexes-and-registries-3\/"},"modified":"2022-04-01T20:17:53","modified_gmt":"2022-04-01T20:17:53","slug":"plaza-college-ht108-health-care-data-indexes-and-registries-3","status":"publish","type":"post","link":"https:\/\/assignmenttutors.net\/blog\/plaza-college-ht108-health-care-data-indexes-and-registries-3\/","title":{"rendered":"Plaza college ht108 health care data, indexes and registries 3"},"content":{"rendered":"<div>\n<p>\u00a0\u00a0<\/p>\n<p><strong>PLAZA COLLEGE<\/strong><\/p>\n<p><strong>HT108 Health Care Data, Indexes and Registries 3 Credits (2 Didactic, 1 Lab)<\/strong><\/p>\n<p><strong>Case Study: <\/strong>\u00a0<strong>ROI Data Dictionary\u00a0<\/strong><\/p>\n<p><strong>Student Name: ___________________________________<\/strong> <strong>Date: ________<\/strong><\/p>\n<p><strong>Domain VI: <\/strong>\u00a0Leadership<\/p>\n<p><strong>Subdomain VI.K.1:<\/strong> \u00a0\u00a0Enterprise Information Management<\/p>\n<p><strong>Competency:<\/strong> \u00a0Apply knowledge of database architecture and design (BL3)<\/p>\n<p><strong>Curricular Consideration: <\/strong>\u00a0Data dictionary and interoperability<\/p>\n<p><strong>Objectives:<\/strong><\/p>\n<p>Explain the concept of data dictionary and interoperability in the process of database implementation and design (VI.K.1- BL3)<\/p>\n<p><u><strong>TASKS<\/strong><\/u><strong>:<\/strong><\/p>\n<p>You have been working with a vendor in the implementation of a new database to track all release of information requests received by your facility. Since you are part of the core team involved in the implementation process, the vendor has requested that you review the data dictionary that will be used as part of the implementation and training for the new database.\u00a0<\/p>\n<p>Review the table below and validate the information being presented to determine if the data elements selected conform to acceptable \u201cgood database design principles.\u201d You must identify any interoperability issues you may anticipate as this database will interphase with other systems used in the organization.<\/p>\n<p>\u00a0\u00a0<\/p>\n<p><strong>Data \u00a0\u00a0Field\u00a0<\/strong><\/p>\n<p><strong>Name<\/strong><\/p>\n<p><strong>Definition<\/strong><\/p>\n<p><strong>Data \u00a0\u00a0Type\u00a0<\/strong><\/p>\n<p>\u00a0<\/p>\n<p>Requested name\u00a0<\/p>\n<p>REQ-NAME<\/p>\n<p>Name of person\/entity requesting \u00a0\u00a0records<\/p>\n<p>Alphanumeric<\/p>\n<p>\u00a0<\/p>\n<p>Patient Name<\/p>\n<p>PT-NAME<\/p>\n<p>Name patient in health record<\/p>\n<p>Alphanumeric<\/p>\n<p>\u00a0<\/p>\n<p>Date Received<\/p>\n<p>DATE-RCD<\/p>\n<p>Date Request was received\u00a0<\/p>\n<p>Date<\/p>\n<p>\u00a0<\/p>\n<p>Date Completed\u00a0<\/p>\n<p>DATE-COMP.<\/p>\n<p>Date Request was completed<\/p>\n<p>Date<\/p>\n<ul>\n<li>Using \u00a0\u00a0\u00a0\u00a0\u00a0Microsoft Word, detail if any issues you are able to identify within the \u00a0\u00a0\u00a0\u00a0\u00a0table presented and discuss any problems you believe could result if this \u00a0\u00a0\u00a0\u00a0\u00a0data dictionary is used for training purposes. You report should also \u00a0\u00a0\u00a0\u00a0\u00a0indicate how the database will be used to interact with other systems in \u00a0\u00a0\u00a0\u00a0\u00a0the organization. If you believe \u00a0\u00a0\u00a0\u00a0\u00a0the table presented does not comply with good database design principles, \u00a0\u00a0\u00a0\u00a0\u00a0indicate which other fields, if any, you would propose to include in the \u00a0\u00a0\u00a0\u00a0\u00a0data dictionary. Explain the reason why you propose these fields.\u00a0<\/li>\n<\/ul>\n<p><u><strong>Standards<\/strong><\/u><strong>: <\/strong>Students must achieve a minimum of 70%.<\/p>\n<p><u><strong>TASKS<\/strong><\/u><strong>:<\/strong><\/p>\n<p>Analysis of proposed table \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0_______\/15<\/p>\n<p>Identify issues with the proposed table _______\/30<\/p>\n<p>Recommend ways to improve the proposed table \u00a0\u00a0\u00a0_______\/30<\/p>\n<p>Demonstrate understanding of interoperability concepts \u00a0\u00a0_______\/20<\/p>\n<p>Correct spelling, punctuation, grammar and formatting ________\/5<\/p>\n<p>Total Points: \u00a0_______\/100<\/p>\n<p><strong>Instructor: ________________________________<\/strong> <strong>Date:_____________<\/strong><\/p>\n<p>\u00a0\u00a0<\/p>\n<p>\u00a0\u00a0<\/p>\n<p><strong>[Hospital Logo]<\/strong><\/p>\n<p>[Insert Manual Name]\u00a0<\/p>\n<p>No. CO-2.010<\/p>\n<p>\u00a0<\/p>\n<p>Title: \u00a0\u00a0<\/p>\n<p>Sentinel Event Response\u00a0<\/p>\n<p>and Reporting\u00a0<\/p>\n<p>Page: 1 of 9<\/p>\n<p>\u00a0<\/p>\n<p>Origination Date: \u00a0\u00a0\u00a002-08-16; 06-19-14;\u00a0<\/p>\n<p>09-21-12; 06-01-08; 07-22-05; 08-15-02; 08-28-00; \u00a0\u00a010-01-96<\/p>\n<p>\u00a0<\/p>\n<p>Effective Date: xx-xx-xx<\/p>\n<p>\u00a0<\/p>\n<p>Retires Policy Dated: xx-xx-xx<\/p>\n<p>\u00a0<\/p>\n<p>Previous Policy Dated: \u00a0xx-xx-xx<\/p>\n<p>\u00a0<\/p>\n<p>Medical Staff\u00a0<\/p>\n<p>Approval Date: \u00a0xx-xx-xx<\/p>\n<p>\u00a0<\/p>\n<p>Hospital Governing\u00a0<\/p>\n<p>Board Approval Date: xx-xx-xx<\/p>\n<p>I. SCOPE:<\/p>\n<p><strong>This policy applies to [insert Hospital name] (\u201cHospital\u201d), its staff, Medical Staff, patients and visitors regardless of service location or category of patient. This policy shall not be used in isolation but as a supplement to the Hospital\u2019s overall Clinical Risk Management\/Patient Safety Plan.<\/strong><\/p>\n<p>II. PURPOSE:<\/p>\n<p>The purposes of this policy are to:<\/p>\n<p>A. Seek to improve patient care by reviewing and responding to Sentinel Events as set forth by The Joint Commission (TJC) Sentinel Event policy and procedures[1] (see <a rel=\"nofollow noopener\" target=\"_blank\" href=\"https:\/\/portal.etenet.com\/Lists\/Policies\/CO-2.010.01_TJC-NQF_Reporting_Requirements.docx\">CO-2.010.01<\/a>);\u00a0<\/p>\n<p>B. Support the improvement of patient safety and quality improvement initiatives by complying with the state-mandated reporting requirements; Hospital will work with Regional Counsel to update policy against state reporting requirements annually (see <a rel=\"nofollow noopener\" target=\"_blank\" href=\"https:\/\/portal.etenet.com\/Lists\/Policies\/CO-2.010.02_Summary_of_State_Reporting_Requirements.docx\">CO-2.010.02<\/a>);\u00a0<\/p>\n<p>C. Support patient safety improvement by reviewing any event which meets the description of any one of the National Quality Forum (NQF) Safe Practices[2] (see <a rel=\"nofollow noopener\" target=\"_blank\" href=\"https:\/\/portal.etenet.com\/Lists\/Policies\/CO-2.010.01_TJC-NQF_Reporting_Requirements.docx\">CO-2.010.01<\/a>); and<\/p>\n<p>D. Evaluate all TJC reviewable Sentinel Events with Home Office Senior Director of Quality Management and Corporate Regulatory Counsel to determine if a voluntary report shall be made to TJC.<\/p>\n<p><strong>III.<\/strong> <strong>DEFINITIONS:<\/strong><\/p>\n<p>A. \u201c<strong>Adverse Event<\/strong>\u201d means an untoward incident, therapeutic misadventure, iatrogenic injury or other unexpected event with the potential for harm that may meet the definition of a Sentinel Event and is directly associated with the care or services provided within the Hospital.<\/p>\n<p>B. \u201c<strong>Anticipated Outcome<\/strong>\u201d means the outcome expected from a diagnostic or therapeutic intervention or lack of intervention. This includes the known risks of a treatment or procedure. Anticipated outcomes, including potential adverse anticipated outcomes, such as known risks, shall be disclosed as part of informed consent and ongoing communication by the provider performing the procedure.<\/p>\n<p>C. \u201c<strong>Care Associated with a Preventable Event<\/strong>\u201d refers to the care directly related to provider error or process failure which resulted in a Preventable Event with Permanent, Severe Temporary, or Temporary Harm.<\/p>\n<p>D. \u201c<strong>Disclosure<\/strong>\u201d means the communication of information regarding the outcome of diagnostic tests, medical treatment, or surgical intervention to a patient and, when appropriate, their families about outcomes of care, including preventable events resulting in harm\/errors.<\/p>\n<p>E. \u201c<strong>Error<\/strong>,\u201d as defined by The Institute of Medicine in 2001, means a failure of a planned action to be completed as intended. Errors are unintended, undesirable, and result from a defect or failure of a diagnostic, therapeutic, or supportive process, at any point in the continuum of care. Errors may be either human or technological. An error may or may not have a negative outcome. Errors may be acts of commission or omission. Many errors are seen as \u201csystem\u201d failures, even when it may appear that a single person or device is at fault. Errors shall be reported by using the Patient Safety Reporting System (PSRS) if they :\u00a0<\/p>\n<p>\u00b7 Require a significant change in further diagnosis or treatment;\u00a0<\/p>\n<p>\u00b7 Lead to initial or prolonged hospitalization;<\/p>\n<p>\u00b7 Are life threatening;\u00a0<\/p>\n<p>\u00b7 Result in disability, death, significant cognitive impairment, or congenital abnormality.\u00a0<\/p>\n<p>F. \u201c<strong>Event Report<\/strong>\u201d means an event report that is completed to document an adverse event or near miss event in the PSRS.\u00a0<\/p>\n<p>G. \u201c<strong>Hospital staff<\/strong>\u201d means the Hospital\u2019s employees, agency staff, contractors and volunteers.<\/p>\n<p>H. \u201c<strong>Intense <\/strong>A<strong>nalysis<\/strong>\u201d means the review process by which all Adverse Events undergo. When events do not meet Sentinel Event criteria for Root Cause Analysis, Intense Analyses can be completed on those events using the Intense Analysis formats available (see Conducting a Root Cause Analysis (RCA) procedure <a rel=\"nofollow noopener\" target=\"_blank\" href=\"https:\/\/portal.etenet.com\/Lists\/Policies\/CO-2.010.03_Conducting_Root_Cause_Analysis.docx\">CO-2.010.03<\/a>). Intense assessments shall be conducted in accordance with state peer review, quality assurance, performance improvement or other state statute.<\/p>\n<p>I. \u201c<strong>Near Miss<\/strong>\u201d means any event with process variation if reoccurrences would carry a significant chance of a serious adverse outcome.<\/p>\n<p>J. \u201c<strong>Outcome of Care<\/strong>\u201d means the result of the performance (or non-performance) of a diagnostic or therapeutic process. Outcomes may be preventable or unpreventable.<\/p>\n<p>K. \u201c<strong>Preventable Event<\/strong>\u201d means an outcome that differs significantly from the anticipated result of a treatment or procedure. A Preventable Event resulting in harm associated with the performance of a treatment or procedure may be negative or positive. Negative Preventable Events resulting in harm are usually considered adverse events. They are usually with an error (American Society for Healthcare Risk Management), and they are not necessarily the result of negligence. A Preventable Event resulting in harm may or may not be considered a reviewable Sentinel Event. Known risks without errors that are common to a procedure do not constitute a Preventable Event resulting in harm or error. Most Preventable Events resulting in harm shall be discussed with the patient; however, those that do not harm the patient and that do not impact current or future patient health care decisions do not need to be disclosed but may be disclosed at the discretion of the responsible health care professional. Preventable Events resulting in harm may involve Hospital staff or physician error in delivery of care and result in patient temporary or significant harm.<\/p>\n<p>L. \u201c<strong>Root Cause Analysis<\/strong>\u201d means a process for identifying the base or contributing causal factors that underlie variations in performance associated with Adverse Events, Sentinel Events or Near Misses (see <a rel=\"nofollow noopener\" target=\"_blank\" href=\"https:\/\/portal.etenet.com\/Lists\/Policies\/CO-2.010.03_Conducting_Root_Cause_Analysis.docx\">CO-2.010.03<\/a>).\u00a0<\/p>\n<p>M. \u201c<strong>Sentinel Event<\/strong>\u201d is a patient safety event not primarily related to the natural course of the patient\u2019s illness or condition that reaches a patient and results in death, permanent harm, or severe temporary harm. (See also <a rel=\"nofollow noopener\" target=\"_blank\" href=\"https:\/\/portal.etenet.com\/Lists\/Policies\/CO-2.010.01_TJC-NQF_Reporting_Requirements.docx\">CO-2.010.01<\/a>.) The PSRS is the mechanism for hospital staff member to complete an event report for patient safety events or near misses (See <a rel=\"nofollow noopener\" target=\"_blank\" href=\"https:\/\/portal.etenet.com\/Lists\/Policies\/CO-2.008_Event_Reporting.docx\">CO.2008 Event Reporting<\/a>).<\/p>\n<p>N. \u201c<strong>Permanent Harm<\/strong>\u201d means death or permanent disability that does not allow a patient to return to his\/her level of activity that existed prior to the event.<\/p>\n<p>O. \u201c<strong>Severe Temporary Harm<\/strong>\u201d is critical, potentially life-threatening harm lasting for a limited time with no permanent residual, but requires transfer to a higher level of care\/monitoring for a prolonged period of time, transfer to a higher level of care for a life-threatening condition, or additional major surgery, procedure, or treatment to resolve the condition.\u00a0<\/p>\n<p>P. \u201c<strong>Temporary Harm<\/strong>\u201d involves limited injury or additional medical treatment needed in response to a preventable event. Patient returns to normal function after a period of time.\u00a0<\/p>\n<p>Q. \u201c<strong>Unanticipated Outcome<\/strong>\u201d means an outcome that is not anticipated in the normal course of the patient\u2019s care.<\/p>\n<p>R. \u00a0\u201c<strong>Unpreventable Event<\/strong>\u201d means an outcome that is within the known risks of the procedure and no error is involved in care delivery. Unpreventable events resulting in harm may result in patient temporary or significant harm.<\/p>\n<p>III. POLICY:<\/p>\n<p>A. The Risk Manager shall utilize the patient safety reporting system (PSRS) to identify, address, document and report to their appropriate Supervisor and, Senior Director of Patient Safety\/Clinical Risk Management of all potential Sentinel Events. In response to each Sentinel Event, the Hospital shall:<\/p>\n<p>1. timely report the event via the PSRS to the Senior Director of Patient Safety\/Clinical Risk Management (see also <a rel=\"nofollow noopener\" target=\"_blank\" href=\"https:\/\/portal.etenet.com\/Lists\/Policies\/CO-2.008_Event_Reporting.docx\">CO-2.008 Event Reporting<\/a>);\u00a0<\/p>\n<p>2. conduct a timely, thorough and credible root cause analysis via Root Cause Meetings within 14 days of the event being identified where attendees are multidisciplinary groups (including Medical Staff) based on the event;<\/p>\n<p>3. \u00a0\u00a0develop an action plan with measurable intermediate and high strength human factor action items designed to implement improvements to reduce risk;\u00a0<\/p>\n<p>4. \u00a0\u00a0implement those improvements; and<\/p>\n<p>5. \u00a0\u00a0monitor the effectiveness of those improvements.<\/p>\n<p>B. Determination of Reporting of Sentinel Events to TJC<\/p>\n<p>The Hospital shall perform a Root Cause Analysis for Sentinel Events and shall evaluate reporting Sentinel Events to TJC after consultation with Home Office Senior Director of Quality Management and Regulatory Counsel.\u00a0<\/p>\n<p>IV. PROCEDURE:<\/p>\n<p>A. Hospital Implementation<\/p>\n<p>The Hospital\u2019s Risk Manager3, Event Manager, or other appropriate person with responsibility for these functions (the \u201cRisk Manager\u201d) shall ensure that the following steps are followed to comply with this policy. Some steps may occur concurrently.<\/p>\n<p>B. Complete an Event Report<\/p>\n<p>1. All Hospital staff are required to report events which reach the level of a Sentinel Event pursuant to the Hospital\u2019s Event Reporting policy (see <a rel=\"nofollow noopener\" target=\"_blank\" href=\"https:\/\/portal.etenet.com\/Lists\/Policies\/CO-2.008_Event_Reporting.docx\">CO-2.008 Event Reporting<\/a>).\u00a0<\/p>\n<p>2. The Risk Manager shall review all event reports to determine whether they meet the definition of a Sentinel Event.\u00a0<\/p>\n<p>3. The Risk Manager shall identify all potential Sentinel Events in the PSRS by completing a Serious Reportable Event cue which shall notify Senior Director of Patient Safety\/Clinical Risk Management.\u00a0<\/p>\n<p>4. For all potential Sentinel Events and Near Misses, the Risk Manager shall ensure that the PSRS contains a description of the event as well as the date of event and medical record number(s).<\/p>\n<p>5. For research subjects involved in a serious adverse event (SAE) the Risk Manager is to be notified along with the principle investigator and Home Office Director of Clinical Research. Refer to policy <a rel=\"nofollow noopener\" target=\"_blank\" href=\"https:\/\/portal.etenet.com\/Lists\/Policies\/CO-2.030_Serious_Adverse_Events_Involving_Research_Study_Patients.docx\">CO-2.030 Serious Adverse Events Involving Research Patients<\/a>.\u00a0<\/p>\n<p>C. Report to the Appropriate Person<\/p>\n<p>1. \u00a0The Risk Manager shall report all potential Sentinel Events to Hospital Administration and the Compliance Officer. The report shall include the following information:<\/p>\n<p>a. Patient name and event date;<\/p>\n<p>b. Description of the event;<\/p>\n<p>c. Current status of the patient and discharge date;<\/p>\n<p>d. If the patient expired, whether the death was related to the natural course of the patient\u2019s underlying condition;<\/p>\n<p>e. If the patient expired, whether the case shall be referred to the medical examiner;<\/p>\n<p>f. \u00a0Whether notification of the event has been made to the patient and\/or family; and<\/p>\n<p>g. Whether the Risk Manager believes that any state or Federal reporting obligations are triggered (<em>i.e.,<\/em> reporting to DHS; reporting restraint deaths to the Centers for Medicare and Medicaid Services (CMS); reporting pursuant to the Safe Medical Devices Act, etc.).<\/p>\n<p>2. The Risk Manager shall also notify:<\/p>\n<p>a. \u00a0Director of Revenue Analysis (DRA) or designee, to place the bill on hold while the potential Sentinel Event is being investigated as described below;\u00a0<\/p>\n<p>b. The Litigation Manager or defense counsel as appropriate; and<\/p>\n<p>c. The Hospital\u2019s Regulatory and Regional Counsel as appropriate.<\/p>\n<p>d. \u00a0Regional Clinical Operations Leadership as appropriate.<\/p>\n<p>D. Complete the Root Cause Analysis and Action Plan<\/p>\n<p>Within fourteen (14) calendar days of the date of event, the Risk Manager shall complete the RCA and human factors based action plan.<\/p>\n<p>E. Billing Procedures for Reviewable Sentinel Events<\/p>\n<p>The Risk Manager shall follow the procedures outlined in Bill Hold Process for Possible Preventable Events resulting in harm <a rel=\"nofollow noopener\" target=\"_blank\" href=\"https:\/\/portal.etenet.com\/Lists\/Policies\/CO-2.010.04_Bill_Hold_Process_for_Possible_Preventable_Events.docx\">CO-2.010.04<\/a> to update accounts placed on bill hold as required by the notification process (see Subsection V.C.2.c.).<\/p>\n<p><strong>F.<\/strong> <strong>Disclose to the Patient\/Family<\/strong><\/p>\n<p>Patients and, when appropriate, their families, shall be promptly informed about the outcomes of care, including preventable events resulting in harm. <u>All<\/u> Preventable Events resulting in harm \u00a0shall be disclosed to the patient. In most cases, the disclosure shall be made in the ordinary course of treatment. The disclosure shall be made as described in Disclosure of Outcomes procedure <a rel=\"nofollow noopener\" target=\"_blank\" href=\"https:\/\/portal.etenet.com\/Lists\/Policies\/CO-2.010.05_Disclosure_of_Outcomes_to_Patients.docx\">CO-2.010.05<\/a> if an occurrence that meets Sentinel Event definition and involves error. <u>Near miss events<\/u> are not included in this disclosure process plan.<\/p>\n<p>G. Immediately Review Restraint Deaths\u00a0<\/p>\n<p>If the potential Sentinel Event involves death in or resulting from restraints (see Clinical Operations policy <a rel=\"nofollow noopener\" target=\"_blank\" href=\"https:\/\/portal.etenet.com\/Lists\/Policies\/CO-4.004_Restraint_and_Seclusion.docx\">CO-4.004 Restraint and Seclusion<\/a> to determine reportability based on type of restraint used),<\/p>\n<p>the Hospital\u2019s Risk Manager shall immediately consult with Home Office Senior Director of Quality or Regional Quality Management to determine whether the restraint death requires a report to CMS in accordance with <a rel=\"nofollow noopener\" target=\"_blank\" href=\"http:\/\/www.ecfr.gov\/cgi-bin\/text-idx?rgn=div5;node=42:5.0.1.1.1;cc=ecfr#42:5.0.1.1.1.2.4.3\">42 C.F.R. 482.13<\/a>.<\/p>\n<p>H. Review Potential Sentinel Events with Regulatory Counsel to Determine State Reporting Obligations<\/p>\n<p>The Risk Manager shall immediately consult with Regulatory Counsel when the Risk Manager believes that state law requires a report of a Sentinel Event.<\/p>\n<p>I. Refer the Event to the Appropriate Medical Staff\/Nursing Committee<\/p>\n<p>If the Event Report requires physician or nursing review, the Risk Manager shall forward the event information to the appropriate medical staff\/nursing review committee for follow-up.<\/p>\n<p>J. Responsible Person\u00a0<\/p>\n<p>The Risk Manager is responsible for ensuring that all individuals adhere to the requirements of this policy, that these procedures are implemented and followed at the Hospital and that instances of non-compliance with this policy are reported to the <u><strong>[insert title of senior individual with leadership\/operational oversight for the area]<\/strong><\/u>.\u00a0<\/p>\n<p>K. Auditing and Monitoring<\/p>\n<p>Audit Services will audit compliance with this policy.<\/p>\n<p>L. Enforcement<\/p>\n<p>All employees whose responsibilities are affected by this policy are expected to be familiar with the basic procedures and responsibilities created by this policy. Failure to comply with this policy will be subject to appropriate performance management pursuant to all applicable policies and procedures, including the Medical Staff Bylaws, Rules and Regulations.\u00a0<\/p>\n<p>V. REFERENCES:<\/p>\n<p>&#8211; <a rel=\"nofollow noopener\" target=\"_blank\" href=\"http:\/\/www.jointcommission.org\/\">The Joint Commission<\/a> (SE Chapter), 2015<\/p>\n<p>&#8211; <a rel=\"nofollow noopener\" target=\"_blank\" href=\"http:\/\/www.qualityforum.org\/\">National Quality Forum Serious Reportable Events, 2012<\/a><\/p>\n<p>&#8211; <a rel=\"nofollow noopener\" target=\"_blank\" href=\"https:\/\/portal.etenet.com\/Lists\/Policies\/COMP-RCC_4.21_Internal_Reporting_of_Potential_Compliance_Issues.pdf\">Regulatory Compliance policy COMP-RCC 4.21 Internal Reporting of Potential Compliance Issues<\/a><\/p>\n<p>&#8211; <a rel=\"nofollow noopener\" target=\"_blank\" href=\"https:\/\/sharepoint.etenet.com\/sites\/ConiferIT\/ConiferStandardTables\/default.aspx\">Payments and Adjustments section, Conifer Standard Tables and Request Forms SharePoint site<\/a><\/p>\n<p>&#8211; <a rel=\"nofollow noopener\" target=\"_blank\" href=\"http:\/\/www.ecfr.gov\/cgi-bin\/text-idx?rgn=div5;node=42:5.0.1.1.1;cc=ecfr#42:5.0.1.1.1.2.4.3\">Medicare Conditions of Participation, Patient Rights 42 C.F.R. 482.13<\/a><\/p>\n<p>&#8211; <a rel=\"nofollow noopener\" target=\"_blank\" href=\"http:\/\/www.cms.gov\/\">Centers for Medicare and Medicaid Services website<\/a>\u00a0<\/p>\n<p><strong>&#8211; <\/strong><a rel=\"nofollow noopener\" target=\"_blank\" href=\"https:\/\/sharepoint.etenet.com\/sites\/Compliance\/ComplianceCentralForms\/Shared%20Documents\/Standards%20of%20Conduct\/SOC-FINAL-110515.pdf\">Standards of Conduct<\/a><\/p>\n<p>&#8211; <a rel=\"nofollow noopener\" target=\"_blank\" href=\"https:\/\/sharepoint.etenet.com\/sites\/Compliance\/ComplianceCentralForms\/Read\/Tenet_Quality_Compliance_Ethics_Program_Charter.pdf\">Quality, Compliance and Ethics Program Charter<\/a><\/p>\n<p>&#8211; <a rel=\"nofollow noopener\" target=\"_blank\" href=\"https:\/\/portal.etenet.com\/Lists\/Policies\/CO-2.010.01_TJC-NQF_Reporting_Requirements.docx\">CO-2.010.01 The Joint Commission\/National Quality Forum Reporting Requirements<\/a><\/p>\n<p>&#8211; <a rel=\"nofollow noopener\" target=\"_blank\" href=\"https:\/\/portal.etenet.com\/Lists\/Policies\/CO-2.010.02_Summary_of_State_Reporting_Requirements.docx\">CO-2.010.02 Summary of State Reporting Requirements<\/a><\/p>\n<p>&#8211; <a rel=\"nofollow noopener\" target=\"_blank\" href=\"https:\/\/portal.etenet.com\/Lists\/Policies\/CO-2.010.03_Conducting_Root_Cause_Analysis.docx\">CO-2.010.03 Conducting a Root Cause Analysis (RCA)<\/a><\/p>\n<p>&#8211; <a rel=\"nofollow noopener\" target=\"_blank\" href=\"https:\/\/portal.etenet.com\/Lists\/Policies\/CO-2.010.04_Bill_Hold_Process_for_Possible_Preventable_Events.docx\">CO-2.010.04 Bill Hold Process for Possible Preventable Events Resulting in Harm<\/a><\/p>\n<p>&#8211; <a rel=\"nofollow noopener\" target=\"_blank\" href=\"https:\/\/portal.etenet.com\/Lists\/Policies\/CO-2.010.05_Disclosure_of_Outcomes_to_Patients.docx\">CO-2.010.05 Disclosure of Outcomes to Patients<\/a><\/p>\n<p>\u00a0\u00a0\u00a0\u00a0<\/p>\n<p>[1]TJC Sentinel Event Policies and Procedures are set forth in the Comprehensive Accreditation Manual for Hospitals, Sentinel Events Chapter.\u00a0<\/p>\n<p>[2]National Quality Forum Safe Practices are available through the NQF website <a rel=\"nofollow noopener\" target=\"_blank\" href=\"http:\/\/www.qualityforum.org\/\">http:\/\/www.qualityforum.org\/<\/a> and are summarized on <a rel=\"nofollow noopener\" target=\"_blank\" href=\"https:\/\/portal.etenet.com\/Lists\/Policies\/CO-2.010.01_TJC-NQF_Reporting_Requirements.docx\">CO-2.010.01<\/a>.\u00a0<\/p>\n<p>3The Hospital\u2019s Patient Safety Officer\/Director of Continuous Quality Improvement may also perform the duties of the Risk Manager described in this policy.<\/p>\n<\/div>\n","protected":false},"excerpt":{"rendered":"<p>\u00a0\u00a0 PLAZA COLLEGE HT108 Health Care Data, Indexes and Registries 3 Credits (2 Didactic, 1 Lab) Case Study: \u00a0ROI Data Dictionary\u00a0 Student Name: ___________________________________ Date: ________ Domain VI: \u00a0Leadership Subdomain VI.K.1: \u00a0\u00a0Enterprise Information Management Competency: \u00a0Apply knowledge of database architecture and design (BL3) Curricular Consideration: \u00a0Data dictionary and interoperability Objectives: Explain the concept of data [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[16],"tags":[],"class_list":["post-47724","post","type-post","status-publish","format-standard","hentry","category-education"],"_links":{"self":[{"href":"https:\/\/assignmenttutors.net\/blog\/wp-json\/wp\/v2\/posts\/47724","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/assignmenttutors.net\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/assignmenttutors.net\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/assignmenttutors.net\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/assignmenttutors.net\/blog\/wp-json\/wp\/v2\/comments?post=47724"}],"version-history":[{"count":0,"href":"https:\/\/assignmenttutors.net\/blog\/wp-json\/wp\/v2\/posts\/47724\/revisions"}],"wp:attachment":[{"href":"https:\/\/assignmenttutors.net\/blog\/wp-json\/wp\/v2\/media?parent=47724"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/assignmenttutors.net\/blog\/wp-json\/wp\/v2\/categories?post=47724"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/assignmenttutors.net\/blog\/wp-json\/wp\/v2\/tags?post=47724"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}