Table Detail Report
OMF_PV_SECURITY_FILTER
| Column Section | Top of Page |
Table-level Detail
| Description: | OMF PowerVision security filter. |
| Definition: | Stores security information (e.g. only show rows in a certain department or from a certain physician group) that was entered using the PowerVision Admin Tool. |
| Table Type: | REFERENCE |
Column Detail - OMF_PV_SECURITY_FILTER
| Column Name | Type | Null? | Definition |
|---|---|---|---|
| GRID_CD | NUMBER | N | Grid which we are placing security on. Other codesets can be used besides 14265 depending on the team defining the value. |
| INDICATOR_CD | NUMBER | Y | Indicator which we are restricting access to. We will add a where clause with this indicator's column_str when the view is run. If a user has no restrictions to the view a single row is placed in this table with an indicator_cd of 0. Other codesets can be used besides 14265 depending on the team defining the value. |
| NUM_ID | NUMBER | Y | Numeric value which is an id from some table. This is the value we are going to restrict on for this person in this view. |
| PARENT_ENTITY_NAME | VC2(40) | Y | Parent entity (table name) that Num_id comes from. Will be used for merging purposes. |
| UPDT_APPLCTX | NUMBER | N | The application context number from the record info block. The UPDT family of columns are typically used for housekeeping and external system process and should never be depended on for solution specific logic. |
| UPDT_CNT | NUMBER | N | Set to 0 on insert. Incremented by 1 on update. Used to recognize update conflict where data in a row updated by one application is at risk of being lost by a second application attempting to update the row. The UPDT family of columns are typically used for housekeeping and external system process and should never be depended on for solution specific logic. |
| UPDT_DT_TM | DATE | N | The date and time the row was last inserted or updated. The UPDT family of columns are typically used for housekeeping and external system process and should never be depended on for solution specific logic. |
| UPDT_ID | NUMBER | N | The person_id of the person from the personnel table (prsnl) that caused the last insert or update of the row in the table. The UPDT family of columns are typically used for housekeeping and external system process and should never be depended on for solution specific logic. |
| UPDT_TASK | NUMBER | N | The registered (assigned) task number for the process that inserted or updated the row. The UPDT family of columns are typically used for housekeeping and external system process and should never be depended on for solution specific logic. |
| USER_ID | NUMBER | N | User id this security is being set up for. |
| VALUE | VC2(255) | Y | Character value to have security on. This column or num_id will be filled out. |
OMF_PV_USER
| Column Section | Top of Page |
Table-level Detail
| Description: | OMF PowerVision User |
| Definition: | Contains a list of all authorized PowerVision users. |
| Table Type: | REFERENCE |
Column Detail - OMF_PV_USER
| Column Name | Type | Null? | Definition |
|---|---|---|---|
| ACTIVE_IND | NUMBER | N | The table row is active or inactive. A row is generally active unless it is in an inactive state such as logically deleted, combined away, pending purge, etc. |
| OMF_PV_USER_ID | NUMBER | N | Unique, generated number that identifies a single row on the OMF_PV_USER table. |
| UPDT_APPLCTX | NUMBER | N | The application context number from the record info block. |
| UPDT_CNT | NUMBER | N | Set to 0 on insert. Incremented by 1 on update. Used to recognize update conflict where data in a row updated by one application is at risk of being lost by a second application attempting to update the row. |
| UPDT_DT_TM | DATE | N | The date and time the row was last inserted or updated. |
| UPDT_ID | NUMBER | N | The person_id of the person from the personnel table (prsnl) that caused the last insert or update of the row in the table. |
| UPDT_TASK | NUMBER | N | The registered (assigned) task number for the process that inserted or updated the row. |
| USER_ID | NUMBER | N | The person who has explicit PowerVision authority. |
OMF_PV_VIEW
| Column Section | Top of Page |
Table-level Detail
| Description: | View definition such as the from and where clauses. |
| Definition: | View definition. |
| Table Type: | REFERENCE |
Column Detail - OMF_PV_VIEW
| Column Name | Type | Null? | Definition |
|---|---|---|---|
| CCL_HINT | VC2(255) | Y | Select statement hint for the view. |
| FROM_CLAUSE | VC2(255) | N | Views from clause. |
| REQUIRED_IND | NUMBER | Y | Indicates whether or not the from/where clause is required for this view. |
| SCRIPT_NBR | NUMBER | Y | Script to run to produce this view. Typically 952287 = omf_run_view. This is not currently checked. |
| STR_SEQ | NUMBER | N | Used for sequencing if "clause" values are greater than 255 characters. |
| UPDT_APPLCTX | NUMBER | N | The application context number from the record info block. |
| UPDT_CNT | NUMBER | N | Set to 0 on insert. Incremented by 1 on update. Used to recognize update conflict where data in a row updated by one application is at risk of being lost by a second application attempting to update the row. |
| UPDT_DT_TM | DATE | N | The date and time the row was last inserted or updated. |
| UPDT_ID | FLOAT | N | The person_id of the person from the personnel table (prsnl) that caused the last insert or update of the row in the table. |
| UPDT_TASK | NUMBER | N | The registered (assigned) task number for the process that inserted or updated the row. |
| VIEW_CD | NUMBER | N | View code value. cdf_meaning='VIEW' and display= |
| WHERE_CLAUSE | VC2(255) | Y | Select statements where clause. |
OMF_RELATIVE_DATES
| Column Section | Top of Page |
Table-level Detail
| Description: | Relative dates. |
| Definition: | Relative date code values and their strings for date ranges such as 'Year to date', 'Last Week', 'Today', etc. |
| Table Type: | REFERENCE |
Column Detail - OMF_RELATIVE_DATES
| Column Name | Type | Null? | Definition |
|---|---|---|---|
| ACTIVE_IND | NUMBER | N | The table row is active or inactive. A row is generally active unless it is in an inactive state such as logically deleted, combined away, pending purge, etc. |
| FROM_DATE_NBR_STR | VC2(255) | Y | The from string for Julian dates. |
| FROM_DATE_STR | VC2(255) | Y | From date string. |
| RELATIVE_DATE_CD | NUMBER | N | Relative date code value. |
| TO_DATE_NBR_STR | VC2(255) | Y | The Julian string for the to date. |
| TO_DATE_STR | VC2(255) | Y | To date string. |
| UPDT_APPLCTX | NUMBER | N | The application context number from the record info block. |
| UPDT_CNT | NUMBER | N | Set to 0 on insert. Incremented by 1 on update. Used to recognize update conflict where data in a row updated by one application is at risk of being lost by a second application attempting to update the row. |
| UPDT_DT_TM | DATE | N | The date and time the row was last inserted or updated. |
| UPDT_ID | NUMBER | N | The person_id of the person from the personnel table (prsnl) that caused the last insert or update of the row in the table. |
| UPDT_TASK | NUMBER | N | The registered (assigned) task number for the process that inserted or updated the row. |
OMF_RULES
| Column Section | Top of Page |
Table-level Detail
| Description: | OMF RULES |
| Definition: | Holds rules which the calc engine uses to determine if a row "qualifies." |
| Table Type: | REFERENCE |
Column Detail - OMF_RULES
| Column Name | Type | Null? | Definition |
|---|---|---|---|
| ACTIVE_IND | NUMBER | Y | The table row is active or inactive. A row is generally active unless it is in an inactive state such as logically deleted, combined away, pending purge, etc. |
| ACTIVE_STATUS_CD | NUMBER | Y | Indicates the status of the row itself (not the data in the row) such as active, inactive, combined away, pending purge, etc. |
| ACTIVE_STATUS_DT_TM | DATE | Y | The date and time that the active_status_cd was set. |
| ACTIVE_STATUS_PRSNL_ID | NUMBER | Y | The person who caused the active_status_cd to be set or change. |
| BEG_EFFECTIVE_DT_TM | DATE | Y | The date and time for which this table row becomes effective. Normally, this will be the date and time the row is added, but could be a past or future date and time. |
| BEG_EVENT_NUM | NUMBER | Y | The first clinical event (e.g. Ordered, Drawn, Verified) defined in the rule - specific to TAT. |
| DESCRIPTION | VC2(80) | Y | Rule/Study description |
| END_EFFECTIVE_DT_TM | DATE | Y | The date/time after which the row is no longer valid as active current data. This may be valued with the date that the row became inactive. |
| PRIORITY | NUMBER | Y | If multiple rules can be used (as in TAT) which will be used first |
| PRODUCT_CD | NUMBER | Y | Product this rule is used with. Typically a code value for Infection Control or TAT |
| PROSE | VC2(255) | Y | The rule as it can be displayed. E.g. Source=Blood and Organism=E. Coli |
| RULE_ID | NUMBER | N | Unique rule identifier |
| RULE_SEQ | NUMBER | N | Used if the rules prose (or other fields) are > 255 characters |
| TIME_BLK_BEG_TIME | VC2(8) | Y | Beginning time of the time block. |
| TIME_BLK_END_TIME | VC2(8) | Y | Ending time of the time block. |
| TIME_BLK_EVENT_NUM | NUMBER | Y | Event number for the beginning of the time block such as for ORDER, DRAWN, COMPLETE, etc. |
| UPDT_APPLCTX | NUMBER | N | The application context number from the record info block. |
| UPDT_CNT | NUMBER | N | Set to 0 on insert. Incremented by 1 on update. Used to recognize update conflict where data in a row updated by one application is at risk of being lost by a second application attempting to update the row. |
| UPDT_DT_TM | DATE | N | The date and time the row was last inserted or updated. |
| UPDT_ID | NUMBER | N | The person_id of the person from the personnel table (prsnl) that caused the last insert or update of the row in the table. |
| UPDT_TASK | NUMBER | N | The registered (assigned) task number for the process that inserted or updated the row. |