|
eMaRC Plus Local Customizations
|
| bet | 32/38 | | Sana | 22.07.2021 | | Hajmi | 0,67 Mb. | | #15596 |
eMaRC Plus can be customized locally by states to change the data items that are stored as discrete fields in the database tables and to change the optionality (Required vs. Optional) of data items.
DATAMAP table: eMaRC Plus program looks to this table to find which HL7 data elements will be stored in which fields of data tables. There are several fields in this table and many of them are just for documentation purpose. For site-specific configuration the following fields are used:
DataTableName: Write the table name where HL7 data element will be stored. MSH, PV1, PID, ORC, OBR, and OBX are valid values.
DataFieldName: Write the field name where HL7 data element will be stored. The field name should exist in the table.
NAACCROpt_xxxx: Optionality column; defines whether data elements are required (R), required when available (R*), or optional (O). You can have a separate optionality column for each laboratory that your site receives messages from. Use PREFERENCES table to show which laboratory will use which optionality column.
For example, if you decide to store PID.3.4 as a separate entity in the database follow these steps:
Open the DATAMAP table and locate PID.3.4 under HL7Element.
Enter PID under DataTableName
Enter AssigningAuthority (or any other name that is meaningful to you) under DataFieldName
Update the optionality column for each laboratory if required to change the default value
Update the length field to indicate the maximum length for this field
Open PID table in the design view and add a field called AssigningAuthority to this table with datatype text (or varchar depending on the database you are using) and the field length specified in step 5 above.
|
| |
