{"aaData": [["100", "
\nThere was a problem with the HL7 EVN Segment. This entry will need to be \nreflagged for transmission.\n\n
\nCorrect the Address - Line 2 through the Patient Demographics protocol.\n\n
\nCorrect the religion code through the Patient Demographics protocol.\n\n
\nCorrect the SSN through the Load/Edit Patient Data protocol, Screen 1,\nGroup 1.\n\n
\nThere was a problem with the HL7 EVN Segment. This entry will need to be reflagged\nfor transmission.\n\n
\nIf the Date if Death is in error, correct through the Death Entry Option \n(Security Key required). If the Encounter date is in error, the\nencounter will need to be deleted and remade.\n\n
\nIf Date of Death is invalid, correct through the Death Entry Option \n(Security Key required). \n\n
\nThe homeless indicator is set through the Social Work Information Management\nSystem (SWIMS). Contact the appropriate personnel to correct this indicator.\n\n
\nCorrect POW status through the Load/Edit Patient Data protocol, Screen 6,\nGroup 2.\n\n
\nContact MCCR to correct this problem.\n\n
\nThis value is set as a default by the software. If invalid, reflag the \nentry for transmission.\n\n
\nCorrect through the Edit Computer Generated Appointment Type on the \nComputer Generated Menu.\n\n
\nCorrect the City name through the Patient Demographics protocol.\n\n
\nThis field is a combination of the Purpose of Visit and the Appointment\ntype, therefore, correction is a two step process. The Purpose of Visit\nis set by the appointment management software and cannot be manually\nchanged. If this field is in error, the appointment will need to be\ndeleted and remade. The Appointment Type can be corrected through the\nEncounter Information protocol. \n\n
\nThis entry is a function of the Clinic set-up parameter 'CLINIC MEETS\nAT THIS FACILITY?:' which must be answered.\n\n
\nRefer to patch SD*5.3*103 to re-link the outpatient encounter to the visit\nentry or delete and remake the appointment.\n\n
\nThis error cannot be corrected through IEMM. It will need to be\ncorrected in the STATION NUMBER (TIME SENSITIVE) file.\n\n
\nIf the encounter date is invalid, or before the date of transmission,\nthe appointment will need to be canceled and remade through\nthe Appointment Manager. It may also be possible that the encounter\nis not acceptable because the activity occurred after the NPCD was closed.\nContact your ADPAC to check on this possibility.\n\n\n
\nThere was a problem with the HL7 DG1 Segment. This entry will need to be \nreflagged for transmission\n\n
\nCorrect diagnosis code through the Check Out protocol.\n\n
\nCurrently this value is a default in the software. If this value is \nincorrect, an error occurred during the build of the HL7 segment. Reflag \nfor transmission.\n\n
\nCorrect diagnosis code through the Check Out protocol. It may be necessary \nto compare what is in scheduling using the Expand Encounter protocol, to \nwhat is in PCE using either Check Out or any of the PCE menu options.\n\n
\nThere was a problem with the HL7 DG1 Segment. This entry will need to be \nreflagged for transmission.\n\n
\nCorrect the State through the Patient Demographics protocol.\n\n
\nCorrect the encounter eligibility code through the Encounter Information\nprotocol.\n\n
\nIf the Veteran status is incorrect, change the status through the\nLoad/Edit Patient Dataprotocol, Screen 7, Group 1. If the Encounter\nEligibility is incorrect, correct through the Encounter Information\nprotocol. \n\n
\nCorrection is made through load/edit Patient Data protocol. An active\nEligibility code needs to be designated. In addition, the eligibility\ncode will have to be updated using the encounter protocol.\n\n
\nCorrect veteran status through Load/Edit Patient Data protocol, Screen 7,\nItem 1.\n\n
\nReview current entries through the Load/Edit Patient Data protocol,\nScreens 6 and 7. \n\n
\nCorrect dependent information through Load/Edit Patient Data protocol\nScreen 8.\n\n
\nCorrect patient Income through Load/Edit Patient Data protocol, Screen 9.\n\n
\n1) Check if a means test is required. A means test can be completed (if\nrequired) through the load/edit Patient Data protocol after the consistency\nchecker has run.\n2) Check if a valid means test existed ON OR BEFORE THE DATE OF ENCOUNTER.\n3) Check if a means test is required and not done/completed.\n4) Check the Eligibility of the Encounter.\n5) Check the Appointment Type of the Encounter.\n\n
\nCompare the dependent information in the Load/Edit Patient Data protocol,\nScreen 8, with the View a Past Means Test option, Screen 1, and correct as\nnecessary.\n\n
\nThere was a problem with the HL7 ZCL Segment. This entry will be \nreflagged for transmission.\n\n
\nCorrect the Zip Code though the Patient Demographics protocol.\n\n
\nCorrect classification question through Load/Edit Patient Data protocol,\nScreens 6 and 7.\n\n
\nReview classification questions through Load/Edit Patient Data protocol,\nScreen 6, Groups 5, 6, and 12, and Screen 7, Group 1.\n\n
\nReview patient information through Load/Edit Patient Data protocol, Screen\n6 Groups 5, 6, 12, and Screen 7 Group 1. Correct inconsistency as needed.\n\n
\nError code no longer used. Entry will be reflagged for transmission.\n Validation Logic: S RES=$$CLAVETSR^SCMSVUT1(VALUE,DFN)\n Correction Logic: S RTN=$$LEDT^SCENIA1\n \n Note: Module CLAVETSTR was removed from routine SCMSVUT1\n \n Original Information\n --------------------\n Description: Vietnam Service indicated inconsistent with classification\n type question\n Corrective Action: Review patient information through Load/Edit Patient\n Data protocol, Screen 6, Groups 4, 5, 6, 12, and\n Screen 7 Group 1. Correct inconsistency as needed.\n\n
\nThere was a problem with the HL7 ZSC Segment. This entry will need to be \nreflagged for transmission\n\n
\nThe stop code must be a valid entry in the CLINIC STOP File. \nUse the Encounter protocol to assign an active/valid stop code.\n\n
\nCorrect service connected question through Load/Edit Patient Data\nprotocol, Screen 7, Group 1.\n\n
\nCorrect service connected percentage through Load/Edit Patient Data\nprotocol, Screen 7, Group 1.\n\n
\nCorrect period of service through Load/Edit Patient Data protocol, Screen\n7, Group 3.\n\n
\nCorrect Vietnam service indicator through Load/Edit Patient Data protocol,\nScreen 6, Group 4.\n\n
\nCorrect the County code through the Patient Demographics protocol.\n\n
\nReview Vietnam service indicator and veteran status through Load/Edit\nPatient Data protocol, Screen 6, Group 4 and Screen 7, Group 1. \n\n
\nCorrect period of service through Load/Edit Patient Data protocol, Screen\n7, Group 3.\n\n
\nCurrently this value is a default in the software. If this value is \nincorrect, an error occurred during the build of the HL7 segment. Reflag \nfor transmission.\n\n
\nCorrect procedure coding through Appointment Management Check Out.\n\n
\nThere was a problem with the HL7 PR1 Segment. This entry will need to be \nreflagged for transmission.\n\n
\nThis problem can be caused by 1) no person class has been designated for\nthe provider or 2) the person class is inactive for the provider. This\nneeds to be referred to the person that is responsible for designating\nperson class for providers.\n\n
\nThere was a problem with the HL7 ZPD Segment. This entry will need to be\nreflagged for transmission\n\n
\nThere was a problem with the HL7 PV1 Segment. This entry will need to be\nreflagged for transmission\n\n
\nThere was a problem with the HL7 PR1 Segment. This entry will need to be\nreflagged for transmission\n\n
\nThere was a problem with the HL7 ZEL Segment. This entry will need to be\nreflagged for transmission\n\n
\nCorrect the patient's marital status through the Patient Demographics protocol.\n\n
\nThere was a problem with the HL7 ZIR Segment. This entry will need to be\nreflagged for transmission\n\n
\nThere was a problem with the HL7 ZCL Segment. This entry will need to be\nreflagged for transmission\n\n
\nThere was a problem with the HL7 ZSC Segment. This entry will need to be\nreflagged for transmission\n\n
\nThere was a problem with the HL7 ZSP Segment. This entry will need to be\nreflagged for transmission\n\n
\nThis error cannot be corrected through IEMM. It will need to be corrected\nin the STATION NUMBER (TIME SENSITIVE) file.\n\n
\nCorrect the clinic stop code through the Encounter Information option.\n\n
\nIf Date of Death is invalid, correct through the Death Entry Option\n(Security Key required). \nIf this LAB encounter is 14 after the date of death, it can not be counted\nfor workload credit.\n\n
\nCorrect the state/county codes through the patient demographic protocol.\n\n
\nReview combat and military service data through the Load/Edit Patient Data\nprotocol, Screen 6.\n\n
\nReview combat and military service data through the Load/Edit Patient Data\nprotocol, Screen 6.\n\n
\nCorrect the patient's religion code through the Patient Demographics protocol\n\n
\nReview combat and military service data through the Load/Edit Patient Data\nprotocol, Screen 6.\n\n
\nCorrect the diagnosis code through the Check Out protocol.\n\n
\nCorrect procedure coding through the Check Out protocol.\n\n
\nThe person class is inactive for the provider. This needs to be referred to\nthe person that is responsible for designating person class for providers.\n\n
\nReview combat and military service data through the Load/Edit Patient Data\nprotocol, Screen 6.\n\n
\n1) Check if a means test is required. A means test can be completed (if\nrequired) through the load/edit Patient Data protocol after the consistency\nchecker has run.\n2) Check if a valid means test existed ON OR BEFORE THE DATE OF ENCOUNTER.\n3) Check if a means test is required and not done/completed.\n4) Check the Eligibility of the Encounter.\n5) Check the Appointment Type of the Encounter.\n\n
\nCorrect classification question through Load/Edit Patient Data protocol, \nScreens 6 and 7.\n\n
\nCorrect the clinic stop code through the Encounter Information option.\n\n
\nCorrect period of service through Load/edit Patient Data protocol, Screen 7, \nGroup3.\n\n
\nContact MCCR to correct this problem.\n\n
\nCorrect the SSN through the Load/Edit Patient Data protocol, Screen 1,\nGroup 1.\n\n
\nThis field is a combination of the Purpose of Visit and the Appointment\ntype, therefore, correction is a two step process. The Purpose of Visit\nis set by the appointment management software and cannot be manually\nchanged. If this field is in error, the appointment will need to be\ndeleted and remade. The Appointment Type can be corrected through the\nEncounter Information protocol.\n\n
\nThis error cannot be corrected through IEMM. It will need to be corrected\nin the STATION NUMBER (TIME SENSITIVE) file.\n\n
\nCorrection is made through load/edit Patient Data protocol. An active\nEligibility code needs to be designated. In addition, the eligibility\ncode will have to be updated using the encounter protocol.\n\n
\nThis information is checked as part of state and county checks.\nNo additional validation logic was entered.\n\n
\nThe insurance type in VISTA does not have an active/inactive flag. No\nvalidation logic was needed.\n\n
\nPurpose of visit does not have an active/inactive flag.\nAppointment Type does have an active/inactive flag, but it is not date\nsensitive. As a result it could not be compare to the encounter date.\nNo validation logic is needed.\n\n
\nThis information is already checked as part of the 5000 error code. At\nthis point no additional validation has been entered.\n\n
\nThis error code is incorporated into 8100.\n\n
\n There was a problem with the HL7 ROL Segment. This entry will be\n reflagged for transmission.\n\n
\n There was a problem with the HL7 ROL Segment. This entry will be\n reflagged for transmission.\n\n
\nCorrect the SSN through the Load/Edit Patient Data protocol, Screen 1,\nGroup 1.\n\n
\n This problem can be caused by no person class being designated for\n the provider or the person class being inactive. This needs to be\n referred to the person responsible for designating Person Class for\n providers.\n\n
\n This problem can be caused by no person class being designated for\n the provider or the person class being inactive. This needs to be\n referred to the person responsible for designating Person Class for\n providers.\n\n
\n Using the Check Out protocol, ensure that one, and only one,\n provider has been denoted as the primary provider for the encounter.\n\n
\n Using the Check Out protocol, ensure that one, and only one,\n provider has been denoted as the primary provider for the encounter.\n\n
\n Using the Check Out protocol, ensure that one, and only one,\n provider has been denoted as the primary provider for the encounter.\n\n
\n This error can not be corrected through IEMM. It needs to be\n corrected in the STATION NUMBER (TIME SENSITIVE) file. Contact your\n MAS ADPAC.\n\n
\n This error can not be corrected through IEMM. It needs to be\n corrected in the STATION NUMBER (TIME SENSITIVE) file. Contact your\n MAS ADPAC.\n\n
\n Using the Check Out protocol, ensure that one, and only one,\n provider has been denoted as the primary provider for the encounter.\n\n
\n There was a problem with the HL7 ROL Segment. This entry will be\n reflagged for transmission.\n\n
\n There was a problem with the HL7 ROL Segment. This entry will be\n reflagged for transmission.\n\n
\nIf the Date of Death is in error, correct through the Death Entry Option\n(Security Key required). If the Encounter date is in error, the\nencounter will need to be deleted and remade.\n\n
\n Review current entry through the Load/Edit Patient Data protocol,\n Screen 6, Group 2.\n\n
\n Review current entry through the Load/Edit Patient Data protocol,\n Screen 6, Group 2.\n\n
\n Review current entries through the Load/Edit Patient Data protocol,\n Screen 6, Group 2.\n\n
\n Review current entries through the Load/Edit Patient Data protocol,\n Screen 6, Group 2.\n\n
\n Review current entry through the Load/Edit Patient Data protocol,\n Screen 6, Group 6.\n\n
\n Review current entries through the Load/Edit Patient Data protocol,\n Screen 6, Group 6.\n\n
\n Review current entry through the Load/Edit Patient Data protocol,\n Screen 6, Group 6.\n\n
\n Review current entries through the Load/Edit Patient Data protocol,\n Screen 6, Group 6.\n\n
\n Review current entry through the Load/Edit Patient Data protocol,\n Screen 6, Group 6.\n\n
\n Review current entry through the Load/Edit Patient Data protocol,\n Screen 6, Group 6.\n\n
\nThere was a problem with the HL7 EVN Segment date. This entry will need to\nbe reflagged for transmission.\n\n
\nIf Date of Death is invalid, correct through the Death Entry Option \n(Security Key required). \n\n
\nEncounter has been marked as being related to combat but patient is not a\ncombat veteran (or was no longer considered a combat veteran at the time\nof the encounter). Review patient information through Load/Edit Patient\nData protocol, Screen 6.\n\n
\nEncounter has been marked as being related to combat but patient is not a\ncombat veteran (or was no longer considered a combat veteran at the time\nof the encounter). Review patient information through Load/Edit Patient\nData protocol, Screen 6.\n\n
\nThe homeless indicator is set through the Social Work Information Management \nSystem (SWIMS). Contact the appropriate personnel to correct this indicator.\n\n
\nCorrect POW status through the Load/Edit Patient Data protocol,\nScreen 6, Group 2.\n\n
\nContact MCCR to correct this problem.\n\n
\nThis value is currently set as a default by the software. Reflag this entry \nfor transmission.\n\n
\nThis field is a combination of the Purpose of Visit and the Appointment\ntype, therefore, correction is a two step process. The Purpose of Visit\nis set by the appointment management software and cannot be manually\nchanged. If this field is in error, the appointment will need to be\ndeleted and remade. The Appointment Type can be corrected through the\nEncounter Information protocol. \n\n
\nCorrect modifier or procedure/modifier combination through the Check Out\nprotocol.\n\n
\nCorrect modifier through the Check Out protocol.\n\n
\nThis value is calculated by the ACRP software. If it is incorrect, an\nerror occurred during the build of the HL7 segment. Reflag for\ntransmission.\n\n
\nThis value is calculated by the ACRP software. If it is incorrect, an\nerror occurred during the build of the HL7 segment. Reflag for\ntransmission.\n\n
\nCorrect procedure/modifier combination through the Check Out protocol.\n\n
\nValid MST Statuses are Y,N,U,D and a blank.\n\n
\nThis entry is a function of the Clinic set-up parameter 'CLINIC MEETS\nAT THIS FACILITY?:' which must be answered.\n\n
\nValid MST Statuses are Y,N,U,D and a blank.\n\n
\nDate in incorrect format or a date appears with an MST status of a\n blank.\n\n
\nDate in incorrect format or a date appears with an MST status of a\n blank.\n\n
\nEncounter is flagged as related to MST, but MST has not been claimed\nPlease correct either the encounter information or the Military Sexual\nTrauma status.\n\n
\nEncounter is flagged as related to MST, but MST has not been claimed\nPlease correct either the encounter information or the Military Sexual\nTrauma status.\n\n
\nRejected by NPCD without a valid reason, use the 'Retransmit Selected Error Code' [SCDX AMBCAR RETRANS ERROR] option to resend.\n\n
\nExposure to Agent Orange can only be claimed by veteran patients that have\na period of service of Vietnam Era (7). Review patient information\nthrough Load/Edit Patient Data protocol, Screen 6, Group 5 and Screen 7,\nGroup 3.\n\n
\nAgent Orange Exposure Location must have a valid value if the patient\nclaims exposure to Agent Orange. If the patient does not claim exposure,\nthan location should not have a value. Review patient informationthrough\nLoad/Edit Patient Data protocol, Screen 6, Group 5\n\n
\nExposure to Agent Orange can only be claimed by veteran patients that have\na period of service of Vietnam Era (7). Review patient information\nthrough Load/Edit Patient Data protocol, Screen 6, Group 5 and Screen 7,\nGroup 3.\n\n
\nAgent Orange Exposure Location must have a valid value if the patient\nclaims exposure to Agent Orange. If the patient does not claim exposure,\nthan location should not have a value. Review patient informationthrough\nLoad/Edit Patient Data protocol, Screen 6, Group 5\n\n
\nRefer to patch SD*5.3*103 to re-link the outpatient encounter to the visit\nentry or delete and remake the appointment.\n\n
\nProvider names can not be numeric. Request that Human Resources correct\nthe provider's name.\n\n
\nAll encounter providers must have an SSN listed in the New Person file \n(#200). Their SSN can not contain 5 or more leading zeros. Request that\nHuman Resources obtain/store the provider's SSN.\n\n
\nProvider names can not be numeric. Request that Human Resources correct\nthe provider's name.\n\n
\nAll encounter providers must have an SSN listed in the New Person file \n(#200). Their SSN can not contain 5 or more leading zeros. Request that\nHuman Resources obtain/store the provider's SSN.\n\n
\nCorrect the patient's ethnicity code through the Patient Demographics\nprotocol of IEMM.\n\n
\nCorrect the patient's ethnicity code through the Patient Demographics \nprotocol of IEMM.\n\n
\nCorrect the Confidential Address - Line 1 through the \nPatient Demographics protocol.\n\n
\nCorrect the Confidential Address - Line 2 through the \nPatient Demographics protocol.\n\n
\nCorrect the Confidential Address - Line 1 through the \nPatient Demographics protocol.\n\n
\nReview combat and military service data through the Load/Edit Patient Data\nprotocol, Screen 6.\n\n
\nThis error cannot be corrected through IEMM. It will need to be\ncorrected in the STATION NUMBER (TIME SENSITIVE) file.\n\n
\nCorrect the Confidential City name through the Patient Demographics \nprotocol.\n\n
\nCorrect the Confidential State through the Patient Demographis protocol.\n\n
\nCorrect the Confidential Zip Code through the Patients Demographic \nprotocol.\n\n
\nCorrect the Confidential County Code through the Patient Demographics \nprotocol.\n\n
\nCorrect the Confidential Address - Line 2 through the Patient Demographic \nprotocol.\n\n
\nCorrect the Confidential City name through the Patient Demographic \nprotocol.\n\n
\nCorrect the Confidential State code through the Patient Demographics \nprotocol.\n\n
\nCorrect Confidential Zip Code through the Patient Demographics protocol.\n\n
\nCorrect the Confidential County code through the Patient Demographics \nprotocol.\n\n
\nIf the encounter date is invalid, or before the date of transmission, the\nappointment will need to be canceled and remade through the Appointment\nManager. \n\n
\nCorrect the Confidential State/County codes through the\nPatient Demographics protocol.\n\n
\nCorrect the Confidential Address Category through the Patient \nDemographics protocol.\n\n
\nCorrect the Confidential Address Start and Stop dates through the Patient \nDemographics protocol.\n\n
\nCorrect the Confidential Address Category through the Patient Demographics \nprotocol.\n\n
\nCorrect the Confidential Address Start and Stop Dates through the\nPatient Demographics protocol.\n\n
\nThere was a problem with the HL7 EVN Segment time. This entry will need to\nbe reflagged for transmission.\n\n
\nTo correct the time of encounter, the appointment will need to be canceled \nand remade through the Appointment Manager.\n\n
\nCorrect the patient's Emergency Response Indicator code through the Patient Demographics protocol.\n\n
\nCorrect the patient's Emergency Response Indicator code through the Patient Demographics protocol.\n\n
\nReview Project 112/SHAD data through the Load/Edit Patient Data protocol,\nScreen 7.\n\n
\nReview Project 112/SHAD data through the Load/Edit Patient Data protocol,\nScreen 7. \n\n
\nCorrect diagnosis code through the Check Out protocol.\n\n
\nCurrently this value is a default in the software. If this value is incorrect, \nan error occurred during the build of the HL7 segment. Reflag for transmission.\n\n
\nCorrect diagnosis code through the Check Out protocol. It may be necessary\nto compare what is in scheduling using the Expand Encounter protocol, to\nwhat is in PCE using either Check Out or any of the PCE menu options.\n\n
\nThere was a problem with the HL7 DG1 segment. This entry should be reflagged \nfor transmission.\n\n
\nCurrently this value is a default in the software. If this value is incorrect, \nan error occurred during the build of the HL7 segment. Reflag for transmission.\n\n
\nCorrect procedure coding through the Check Out protocol.\n\n
\nThis problem can be caused by 1) no person class has been designated for\nthe provider or 2) the person class is inactive for the provider. This\nneeds to be referred to the person that is responsible for designating\nperson class for providers.\n\n
\nCorrect patient name through Load/Edit Patient Data protocol, Screen 1,\nGroup 1\n\n
\nThere was a problem with the HL7 PR1 segment. This entry should be \nreflagged for transmission.\n\n
\nCorrect the encounter eligibility code through the Encounter Information\nprotocol.\n\n
\nIf the Veteran status is incorrect, change the status through the\nLoad/Edit Patient Data protocol, Screen 7, Group 1. If the Encounter\nEligibility is incorrect, correct through the Encounter Information\nprotocol. \n\n
\nCorrect veteran status through Load/Edit Patient Data protocol, Screen 7,\nGroup 1.\n\n
\nReview current entries through the Load/Edit Patient Data protocol,\nScreens 6 and 7. Correct these entries as necessary.\n\n
\nCorrect dependent information through Load/Edit Patient Data protocol,\nScreen 8.\n\n
\nReview the dependent information in the Load/Edit Patient Data protocol,\nScreen 8, with the information in the View a Past Means Test option,\nScreen 1, and correct as necessary.\n\n
\n1) Check if a means test is required. A means test can be completed (if\nrequired) through the load/edit Patient Data protocol after the consistency\nchecker has run.\n2) Check if a valid means test existed ON OR BEFORE THE DATE OF ENCOUNTER.\n3) Check if a means test is required and not done/completed.\n4) Check the Eligibility of the Encounter.\n5) Check the Appointment Type of the Encounter.\n\n
\nCorrect patient Income through Load/Edit Patient Data protocol, Screen 9.\n\n
\nReview classification questions through Load/Edit Patient Data protocol,\nScreen 6, Groups 5, 6, and 12, and Screen 7, Group 1.\n\n
\nReflag this entry for retransmission. If the error still occurs, you\nmay need to delete and re-enter the check out.\n\n
\nReview patient information through Load/Edit Patient Data protocol, Screen\n6 Groups 5, 6, 12, and Screen 7 Group 1. Correct inconsistency as needed.\n\n
\nCorrect classification question through Load/Edit Patient Data protocol,\nScreens 6 and 7.\n\n
\nThere was a problem with the HL7 ZCL segment. This entry will be \nreflagged for transmission.\n\n
\nThere was a problem with the HL7 BHS Segment. This entry will need to be\nreflagged for transmission\n\n
\nThere was a problem with the HL7 MSH Segment. This entry will need to be \nreflagged for transmission\n\n
\nThis entry will need to be reflagged for transmission.\n\n
\nThere was a problem with the HL7 EVN Segment. This entry will need to be \nreflagged for transmission\n\n
\nThere was a problem with the HL7 PID Segment. This entry will need to be \nreflagged for transmission\n\n
\nThere was a problem with the HL7 ZPD Segment. This entry will need to be \nreflagged for transmission\n\n
\nThere was a problem with the HL7 PV1 Segment. This entry will need to be \nreflagged for transmission\n\n
\nCorrect Date of Birth (DOB) through Load/Edit Patient Data protocol, Screen\n1, Group 1.\n\n
\nThere was a problem with the HL7 PR1 Segment. This entry will need to be \nreflagged for transmission\n\n
\nThere was a problem with the HL7 ZEL Segment. This entry will need to be \nreflagged for transmission\n\n
\nThere was a problem with the HL7 ZIR Segment. This entry will need to be \nreflagged for transmission\n\n
\nThere was a problem with the HL7 ZCL Segment. This entry will need to be \nreflagged for transmission\n\n
\nThere was a problem with the HL7 ZSC Segment. This entry will need to be \nreflagged for transmission\n\n
\nThere was a problem with the HL7 ZSP Segment. This entry will need to be \nreflagged for transmission\n\n
\nThere was a problem with the HL7 EVN Segment. This entry will need to be \nreflagged for transmission\n\n
\nThere was a problem with the HL7 PID Segment. This entry will need to be \nreflagged for transmission\n\n
\nThere was a problem with the HL7 ZPD Segment. This entry will need to be \nreflagged for transmission\n\n
\nThere was a problem with the HL7 PV1 Segment. This entry will need to be \nreflagged for transmission\n\n
\nCorrect the patient's sex code through the Patient Demographics protocol.\n\n
\nThere was a problem with the HL7 BTS Segment. This entry will need to be \nreflagged for transmission\n\n
\nThis entry will need to be reflagged for transmission\n\n
\nThe stop code must be a valid entry in the CLINIC STOP File.\nUse the Encounter protocol to assign an active/valid stop code.\n\n
\nThere was a problem with the HL7 ZSC Segment. This entry will need to be \nreflagged for transmission\n\n
\nCorrect service connected question through Load/Edit Patient Data\nprotocol, Screen 7, Group 1.\n\n
\nCorrect service connected percentage through Load/Edit Patient Data\nprotocol, Screen 7, Group 1.\n\n
\nCorrect invalid period of service through Load/Edit Patient Data protocol,\nScreen 7, Group 3.\n\n
\nCorrect Vietnam service indicator through Load/Edit Patient Data protocol,\nScreen 6, Group 4.\n\n
\nReview Vietnam service indicator and veteran status through Load/Edit \nPatient Data protocol, Screen 6, Group 4 and Screen 7, Group 1. \n\n
\nThere was a problem with the HL7 transmission. This entry will need to be \nreflagged for transmission\n\n
\nCorrect the patient's Race code through the Patient Demographics protocol\nof IEMM.\n\n
\nThere was a problem with the HL7 DG1 Segment. This entry will need to be \nreflagged for transmission\n\n
\nThis patient has been reported dead by another facility. The reporting \nfacility will need to be determined from the NPCD and contacted for \nadditional information.\n\n
\nError code no longer used. Entry will be reflagged for transmission.\n Correction Logic: S RTN=$$LEDT^SCENIA1\n \n Original Information\n --------------------\n Description: Vietnam Service indicated inconsistent with classification\n type question\n Corrective Action: Correct inconsistency between Vietnam service and\n agent orange classification through Load/Edit Patient\n Data protocol, Screen 6, Groups 4 and 5.\n\n
\nPlease note this error and report it to your supervisor for review. This \nerror cannot be 'corrected' through IEMM.\n\n
\nThis entry will need to be reflagged for transmission.\n\n
\nThere was a problem with the HL7 EVN segment. This entry should be \nreflagged for transmission.\n\n
\nIf the event date/time is missing or invalid, the problem may have been \nwith the HL7 transmission. This entry should be reflagged for transmission.\nIf the event date is before 10/1/96, this entry cannot be sent.\n\n
\nReflag this entry for retransmission. If the error still occurs, you\nmay need to delete and re-enter the check out.\n\n
\nCorrect patient name through Load/Edit Patient Data protocol, Screen 1,\nGroup 1.\n\n
\nThere was a problem with the HL7 PID Segment. This entry will need to be\nreflagged for transmission\n\n
\nCorrect the Address - Line 1 through the Patient Demographics protocol.\n\n
\nCorrect Date of Birth (DOB) through Load/Edit Patient Data protocol,\nScreen 1, Group 1\n\n
\nCorrect the patient's sex code through the Patient Demographics Protocol.\n\n
\nCorrect the patient's race code through the Patient Demographics protocol\nof IEMM.\n\n
\nCorrect the Address - Line 1 through the Patient Demographics protocol.\n\n
\nCorrect the Address - Line 2 through the Patient Demographics protocol.\n\n
\nCorrect the City name through the Patient Demographics protocol.\n\n
\nCorrect the State through the Patient Demographics protocol.\n\n
\nCorrect the Zip Code though the Patient Demographics protocol.\n\n
\nCorrect the County code through the Patient Demographics protocol.\n\n
\nCorrect the marital status through the Patient Demographics protocol.\n\n