Hierarchy
⤷ IS-H-PM (Application Component) Patient Management
⤷ N1CORDMG (Package) IS-H: Clinical Ordering; TSA Development
Basic Data
Data Element | N1COTSTAENDDT |
Short Description | IS-H: CORD/PREG: Val. End Status Profile-Order Type Asgmt |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | RI_DATUM | |
Data Type | DATS | Date field (YYYYMMDD) stored as char(8) |
Length | 8 | |
Decimal Places | 0 | |
Output Length | 10 | |
Value Table |
Further Characteristics
Search Help: Name | ||
Search Help: Parameters | ||
Parameter ID | ||
Default Component name | ||
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | Valid To |
Medium | 14 | Valid To |
Long | 20 | Valid To |
Heading | 10 | Valid To |
Documentation
Definition
End of the validity of a status profile-to-order type assignment.
Note on clinical order and preregistration: The preregistration is a kind of clinical order. SAP Patient Management (IS-H) only uses Preregistration, whereas ISHMED also uses other kinds of clinical order. Therefore explanations for IS-H always concern the preregistration.
Use
You can define different status profiles with different validity periods for a clinical order.
When an order item of a clinical order is created, the system uses the status profile that is defined for this point in time as valid for the corresponding order type. This status profile applies for the entire life cycle of the order item, independently of the validity of the assignment to the order type.
Consequently you must have assigned a status profile to the clinical order for each point in time of the order's validity.
Dependencies
Example
History
Last changed by/on | SAP | 20050224 |
SAP Release Created in | 472 |