Case Cart Header
The Case Cart Header file contains key information for each case. Each record contains basic information on the patient and the case. With Lawson-defined relations to other files, this is the primary file for the case structure. You add data to this file using a manual, automatic, or combined process. Use CX20.1 (Case Build) to manually add or delete case header information. Run CX506 (HL7 Schedules Import Interface) to automatically import header data from an outside scheduling system. To upload ADT information and then add the uploaded cases and patients, run PC520 (Patient Upload), then PC521 (Patient Interface), and then use CX20.1. For information on using the Patient Charge programs, see the Inventory Control Procedures Manual. You delete case information, which includes header information in this file, using CX20.1. (A case consists of one or more practitioner-specific preference templates assigned to a patient visit and related header data.) Fields in each record include information on the case visit such as company and requesting location, start and completion dates, total cost breakdown, and so on. The completion date is a user-defined date added in CX30.1 (Case Completion Feedback) when finishing a case. Note that for stock or non-inventory tracked stock on hand, you must use a Warehouse system picking process to close out all demand before you can finish a case. (For instructions on completing a case, see the Case Carts Procedures Manual.)
REFERENCED BY
| CX225 | CX230 | CX235 | CX240 | CX50.1 | CX55.1 |
| PO23.1 | PC310 | PC521 |
| FIELD NAME | DESCRIPTION/VALID VALUES | UPDATED BY | |
|---|---|---|---|
| CXH-COMPANY Element: Company | Numeric 4 This field contains the company number. Valid values are Any Case Carts system company, defined in CX01.1 (Healthcare Company) with an equivalent Inventory Control company in IC01.1 (Company). |
||
| CXH-REQ-LOCATION Element: Req Location | Alpha 5 This field contains the location requisitioning items and receiving charges for the items. This location can be an inventory or noninventory location. This value appears as the to location on the pick lists printed when you run CX100 (Pick List Print) and WH130 (Pick List Print). Valid values are A requesting location defined in RQ01.1 (Requesting Location) for the specified healthcare company. |
||
| CXH-CASE Element: Case | Alpha 15 This field contains the unique, user-assigned identifier for the case. A case identifier is used in the Case Carts system to associate specific tasks, practitioners, preference lists, and other information with a particular treatment course. This treatment course may consist of one or more procedures. The Case Carts system uses the case number to interface with an outside scheduling system. |
||
| CXH-SUITE Element: Suite | Alpha 5 This field contains the specific location ID for the surgery suite, patient room, and so on. The Case Carts system can import the suite number from an outside scheduling system. |
||
| CXH-VISIT-NBR Element: Visit Nbr | Alpha 12 This field contains the identifier that makes a visit unique with a company. The Case Carts system can import this value from an outside scheduling system. Alternatively, when using CX20.1 (Case Build), you can select a value from the Patient Charge system for assignment to the case. |
||
| CXH-PATIENT-ID Element: Patient Id | Alpha 12 This field uniquely identifies a patient within a company. The Case Carts system can import this value from an outside scheduling system. Alternatively, when using CX20.1 (Case Build), you can select a value from the Patient Charge system for assignment to the case. |
||
| CXH-CX-START-TIME Element: Actual Time | Numeric 4 This field contains the start time for the case. |
||
| CXH-START-DATE Element: Start Date | Numeric 8 (yyyymmdd) This field contains the date when the case starts. This value is used in CX206 (Case Value Report) or the Case Carts Analyzer to report on how long procedures are taking to complete For instructions on using these programs, see the Case Carts Procedures Manual. |
||
| CXH-COMPLETED-TIME Element: Actual Time | Numeric 4 This field contains the completion time for the case. This value is a user-defined time added in CX30.1 (Case Completion Feedback) when finishing a case. |
||
| CXH-COMPLETED-DATE Element: Completed Date | Numeric 8 (yyyymmdd) This field contains the completion date for the case. For cases assigned multiple procedures, this date equals the procedure completion date of the procedure assigned the final preference sequence number on the case. (The completion date is a user-defined date added in CX30.1 (Case Completion Feedback) when finishing a case.) |
||
| CXH-SERVICE-DATE Element: Service Date | Numeric 8 (yyyymmdd) This field identifies the date the item was used. This date is used by the billing system to identify the charges associated with this case. In the Patient Charge system, this date is called the Charge Date. |
||
| CXH-STATUS Element: Status | Numeric 1 This field contains the case transaction status. You can continue to change a case until the status has changed to 4 (Charges Passed) or 5 (No Charges). Note: If you add or change a line that is to be picked and the case status is 3 (Complete), the case status returns to 2 (Released). This status appears in case inquiry forms, such as CX20.1 (Case Build) and CX50.1 (Preference List Status). It is updated from the Warehouse system. The status helps you to determine when to pick items or close demand records. CX30.1 (Case Completion Feedback) displays this value. To finish a case, this status must be set to Complete. 1 = Unreleased 2 = Released 3 = Complete 4 = Charges Passed 5 = No Charges |
||
| CXH-PRINT-FLAG Element: Print Flag | Alpha 1 This field contains Yes or No. The value indicates whether to print the Preference/Case listing using CX220 (Case/Preference Listing). Y = Yes N = No |
||
| CXH-OPERATOR-ID Element: Operator | Alpha 10 This is the terminal signon identifier that was active when this update to the database was performed. |
||
| CXH-LAST-PREF-SEQ Element: Seq | Numeric 3 This field contains the record sequence number. The Case Carts system uses this value to track placement of procedures in a multiprocedure case. View and add these values in CX20.2 (Case Detail) and CX30.1 (Case Completion Feedback). |
||
| CXH-LAST-ALT-LINE Element: Line Nbr | Numeric 6 This field contains the last alternative line. The system uses this value to track multiple procedures on a case. |
||
| CXH-AUTO-REDUCTION Element: All Flag | Alpha 1 This field is reserved for a future release of the Case Carts system. Y = Yes N = No |
||
| CXH-NORMAL-TIME Element: Actual Time | Numeric 4 This field contains the user-defined typical time to complete a procedure. |
||
| CXH-SALARY-RANGE Element: Sal Range Fl | Alpha 1 This field contains the indicator for the salary range used for cost analysis. This is the default salary range the Case Carts system logic uses when defaulting labor costs to preference templates and patient cases. 1 = Min 2 = Mid 3 = Max |
||
| CXH-CLINICAL-CST Element: Intl Amt | Signed 18.2 This field contains the sum of the user-defined clinical costs for each case preference. When you add a case using CX20.1 (Case Build), the Case Carts system totals the applicable clinical costs from the Case Cart Preferences file to get this value. Change this value indirectly in one of two ways. The first way is to use CX05.1 (Preference Template) to change the clinical costs on the applicable template and then delete and re-add the template to the applicable case using CX20.1 (Case Build). The second way is to type new values in the Procedure Cost tab of CX20.2 (Case Detail). In the second way, the costs are recorded for the case preference only and are not captured in templates for future use. Note: To view this value, use one of the following features: the Drill Around (F5) feature in the Pref Code field of CX20.1 (Case Build), the Case Carts Analyzer, or a file editor. |
||
| CXH-DIST-CST Element: Intl Amt | Signed 18.2 This field contains the sum of the user-defined distribution costs for each case preference. When you add a case using CX20.1 (Case Build), the Case Carts system totals the applicable distribution costs from the Case Cart Preferences file to get this value. Change this value indirectly in one of two ways. The first way is to use CX05.1 (Preference Template) to change the distribution costs on the applicable template and then delete and re-add the template to the case. The second way is to type new values in the Procedure Cost tab of CX20.2 (Case Detail). In the second way, the costs are recorded for the case preference only and are not captured in templates for future use. Note: To view this value, use one of the following features: the Drill Around (F5) feature in the Pref Code of CX20.1 (Case Build), the Case Cart Analyzer, or a file editor. |
||
| CXH-SUPPLY-CST Element: Intl Amt | Signed 18.2 This field contains the sum of the user-defined supply costs for items on a case. (A preference is a preference template attached to a case.) This value is updated each time any item cost-related element is changed by adding, deleting, changing quantity, and so on. When you add a case using CX20.1 (Case Build), the Case Carts system totals the applicable supply costs (Issue Costs) in the Preference Items file to get this value. Inquire on CX20.2 (Case Detail) to view each supply cost value of the Preference Items file. View each supply cost in the Items tab, in the Cost field of the Detail detail tab for each item. Change this value indirectly in one of two ways. The first way is to use CX05.1 (Preference Template) to change the supply costs on the applicable template and then reassign the template to and change the case. The second way is to use CX20.2 (Case Detail) to type new values in the Cost field of the Items tab, Detail detail tab for each applicable item. In the second way, the costs are recorded for the case preference only and are not captured in templates for future use. Note: To view this value, use one of the following features: the Drill Around (F5) feature in the Pref Code field of CX20.1 (Case Build), the Case Carts Analyzer, or a file editor. |
||
| CXH-TOTAL-CST Element: Intl Amt | Signed 18.2 This field contains the total of all costs for a procedure. The costs included are those for supplies (items), burden, clinical resources, and distribution resources. This value is updated each time any cost-related element is changed on a case by adding, deleting, changing quantity, and so on. Note: To view this value, use one of the following features: the Drill Around (F5) feature in the Pref Code field of Case Build (CX20.1), the Case Carts Analyzer, or a file editor. |
||
| CXH-TOTAL-BURDEN Element: Intl Amt | Signed 18.2 This field contains the total costs associated with procedure burden codes. A burden is a resource with a measurable cost assigned to a case. The measurable cost can be an indirect cost, assigned to but not directly related to a case. Examples of burden are salaries, equipment, services, and other indirect costs for capital depreciation, building management, and so on. Use CX15.1 (Burden) or CX504 (HR Labor Import) to define burden codes. Use CX15.1 to view burden codes. Note: To view this value, use one of the following features: the Drill Around (F5) feature in the Pref Code field of CX20.1 (Case Build), the Case Carts Analyzer, or a file editor. |
||
| CXH-PK-PRINT-FLAG Element: Pk Print Flag | Alpha 1 Select the proper value to create a pick ticket, post items, or complete the case. 1 = Create Pick List 2 = Process Post Items 3 = Complete 4 = Reprocess |
||
| CXH-PATIENT-CLASS Element: Patient Class | Alpha 1 This field provides for a category of patient. I = Inpatient O = Outpatient B = Both |
||
| CXH-ONLINE-ALLOCAT Element: All Flag | Alpha 1 This field indicates whether to allow online or batch allocation. Select Yes to allow online allocation. If you select Yes, when you release the case, the Case Carts system tries to allocate all items to the requesting location. Select No to allow batch allocation. If you select No, when you release the case, you must run WH110 (Batch Allocation) to allocate inventory items for the case. Y = Yes N = No |
||
| CXH-LAST-REF-NBR Element: Last Ref Nbr | Numeric 9 This field contains the last reference number. The system uses this value with the Reference Number value in the Case Cart Preference Items file to interface with WH130 (Pick List Print). |
||
| CXH-AM-PM-FLAG Element: Am Pm Flag | Alpha 2 This field indicates whether the case start time is for the morning or for the afternoon or evening. AM = AM PM = PM |
||
| CXH-COMPL-AM-PM Element: Compl Am Pm | Alpha 2 This field indicates whether the case completion time is for the morning or for the afternoon or evening. AM = AM PM = PM |
|
|
| CXH-FICA-NBR Element: Fica Nbr | Alpha 20 |
|
|
| CXH-FLAT-FEE-FL Element: Flat Fee Fl | Alpha 1 N = No Y = Yes |
||
| CXH-AUTO-TOTAL Element: Auto Total | Alpha 1 |
||
| CXH-ACCT-CATEGORY Element: Acct Category | Alpha 5 Account categories are groupings of costs, revenues, or a combination of both used for reporting and inquiries for activities in the Activity Management system. All transactions are posted to an account category within an activity. You can assign a specific General Ledger account or range of accounts (company, accounting unit, account, and subaccount) that make up the transactions posted to an account category using AC07.1 (Account Assignment). Period-to-date, year-to-date, and life-to-date balances are maintained by account category for activities. Account categories must be assigned to activities before you do any budgeting or transaction processing. Valid account category types are: cost revenue accrual pass thru |
||
| CXH-ACTIVITY Element: Activity | Alpha 15 Activities are the processes or procedures that produce work. Cost objects (products, services, customers, and so on) are the reasons for performing the activity. |
||
| CXH-ATN-OBJ-ID Element: Obj Id | Numeric 12 This is the object identifier. It is used to relate commitments or posted transactions back to the originating subsystems. Each subsystem record that is updated as a commitment or posted transaction is assigned an object identifier. The object identifier is maintained in the subsystem files and in the Activity Commitments Detail and Activity Transaction files. The object identifier is a unique key used to drill back from Activity Management to the subsystems. |
| NAME | KEY FIELDS | DESCRIPTION / SUBSET CONDITION | USED IN | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| CXHSET1 |
COMPANY REQ-LOCATION CASE |
|
||||||||||||||
| CXHSET2 |
COMPANY REQ-LOCATION START-DATE CASE |
|
| |||||||||||||
| CXHSET3 |
COMPANY VISIT-NBR REQ-LOCATION CASE |
|
| |||||||||||||
| CXHSET4 |
COMPANY REQ-LOCATION STATUS COMPLETED-DATE START-DATE CASE |
|
| |||||||||||||
| CXHSET5 |
COMPANY CASE REQ-LOCATION |
|
||||||||||||||
| CXHSET6 |
ATN-OBJ-ID |
|
||||||||||||||
| RELATION NAME |
RELATED FILE | INTEGRITY RULES / FIELD MATCH | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Cxcompany | CXCOMPANY |
Required
| |||||||||
| Hcpatient | HCPATIENT |
Required
| |||||||||
| Reqlocation | RQLOC |
Required
| |||||||||
| Whdemndhdr | WHDEMNDHDR |
Not Required
|
| RELATION NAME |
RELATED FILE | INTEGRITY RULES / FIELD MATCH | |||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Cccasepref | CXCASEPREF |
Delete Cascades
| |||||||||||||||
| Whshipment | WHSHIPMENT |
|
All trademarks and registered trademarks are the property of their
respective owners.