HomeHealthAgencyFacilityConfiguration
Contains Home Care facility no-add single items information.
| Column Name | Type | Description |
|---|---|---|
| PhysicalDeploymentOwnerIdentifier | VARCHAR | ID of the physical deployment owner for this record. Physical owners will be where the data is hosted, either on the cross-over server or the owner deployment. Links to table CL_COMMUNTY_INSTNC. |
| DeferredReferralDateQuestionIdentifier | VARCHAR | Identifies the customer owned question (LQL) record which will discretely document the date when a referral will be deferred to. |
| HomeHealthAdmissionLogicProgrammingPointIdentifier | NUMERIC | A programming point (LPP record) that should be executed as part of an admission to home health. This will be executed after the standard admission logic has taken place. Links to table CLARITY_LPP. |
| OasisPatientFilePath | VARCHAR | The path to the file that contains information for the beginning of each body record in the OASIS file. This file will be used for OASIS data submission. |
| AllowReferralSourceCreationOnTheFly | INTEGER | This setting configures whether or not users in the Home Health intake module are able to create referral source records on the fly. Records created in this fashion will be marked as unverified. The Unverified Referral Source report can then be used to report on the unverified records in the master file. Links to category table ZC_ALLW_RFL_CREATE. |
| HomeHealthScheduleVisitTypeIdentification | VARCHAR | The default Cadence visit type for EpicCare Home Health contacts. |
| ResumptionOfCareProcedureIdentifier | NUMERIC | ROC Procedure to EAP Mapping. Links to table CLARITY_EAP. |
| HomeCareEpisodeCreation | NUMERIC | Programming Point to run after a Home Care episode is created. |
| FacilityIdentifier | NUMERIC | The unique identifier for the facility record. |
| HomeHealthFollowupProcedureIdentifier | NUMERIC | HH Follow-up Assessment to EAP Mapping. Links to table CLARITY_EAP. |
| OrderReplyPoolIdentification | NUMERIC | The pool to which verbal order alerts will be sent when a physician electronically signs a verbal order. |
| CaseManagerDiscipline | INTEGER | The discipline that is used for case managers. This will determine which member of the care team is displayed under the title of case manager in the Home Health Episode of Care History table. Links to table ZC_DISCIPLINE. |
| OasisHeaderFilePath | VARCHAR | The path to the file that contains agency-specific OASIS information. This file will be used for the header record for OASIS file submission. |
| MedicareProgrammingPointIdentification | NUMERIC | Programming Point used to find medicare and medicaid numbers |
| HomeHealthPaymentClassificationMappingRecordIdentifier | VARCHAR | The PCM (Payment Classification Mapping) record to be used by Home Health. The PCM record contains the standardized prospective payment rate, and also indicates the percentage of the payment that's labor related. |
| SendVerbalOrderAlertMessageToResponsiblePersonFlag | VARCHAR | Controls whether to send an order alert message to the responsible person when a physician electronically signs a verbal order. |
| FacilityMedicareProviderNumber | VARCHAR | The agency Medicare provider number for your facility. This piece of data will be used in field (M0010) of the OASIS data set. The agency Medicare provider number is a 6 digit identifier, and cannot contain any spaces, letters, or punctuation. |
| VerbalOrderNoteMessageSentIndicator | VARCHAR | Controls whether a message is sent for signed verbal orders only when the physician has created an Order Note. |
| IsEpisodeTypeVisibleInIntake | VARCHAR | Controls whether the Episode Type field will be visible in Intake in the Episode of Care Information form. |
| HomeHealthDischargeProgrammingPointIdentification | NUMERIC | A programming point (LPP record) that should be executed as part of a discharge from home health. This will be executed after the standard discharge logic has taken place. Links to table CLARITY_LPP. |
| AgencyNationalProviderIdentifier | VARCHAR | Agency National Provider ID |
| AgencyMedicaidProviderNumber | VARCHAR | The agency Medicaid provider number for your facility. This piece of data will be used in field (M0012) of the OASIS data set. The agency Medicaid provider number is a 15 digit identifier, and cannot contain any spaces, letters, or punctuation. |
| PlanOfCareProgrammingPointIdentification | NUMERIC | The Plan of Care Programming point, which determines how medications, orders and goals are generated on the Home Health Plan of Care. |
| HomeHealthPlanOfCareMessageType | NUMERIC | Holds a custom IB message type to use for route to MR instead of staff message |
| StartOfCareProcedureIdentifier | NUMERIC | SOC assessment to EAP Mapping. Links to table CLARITY_EAP. |
| ServiceIntensityAddonProcedureId | NUMERIC | Stores the procedure definition for the Service Intensity Add-on charge. Links to table CLARITY_EAP. |
| HomeHealthErroneousTypeOfServiceCategory | INTEGER | The type of service category used to designate Home Health encounters as "erroneous". This helps in the identification of erroneous encounters in other parts of the application, such as Chart Review. |
| TravelUnavailableReasonCode | INTEGER | The unavailable reason that is used to set time off in the schedule for travel between appointments and staff activities. |
| LogicalDeploymentOwnerIdentifier | VARCHAR | ID of the logical deployment owner for this record. Logical owners show the deployment where the record was created but don't represent if the record is a part of version skew. Links to table CL_COMMUNTY_INSTNC. |
| AgencyUseProgrammingPointIdentifier | NUMERIC | The programming point to be used to enter data in the OASIS field AGENCY_USE. |
| HideSignsOfDeathQuestion | INTEGER | The "Signs of clinical death observed upon arrival?" question appears for visits that span the time of death. If that question is answered Yes, the full visit will be classified as post-mortem. If that question is answered No, the Time of Death will be used to split the visit into pre and post mortem charges. This setting will determine if the "Signs of clinical death observed upon arrival?" question will be used and appear in the Remote Client. If set to 0-Question in contact, or left blank, the question will be required in visit documentation to determine the pre-mortem and post-mortem charges. If set to 1-Always use documented Time of Death, the question will not be used in the Remote Client and the Time of Death will determine the pre-mortem and post-mortem charges. |