| Topics | Data Mapping | Search: |
| When data is imported from HL7 messages, there could
be a number of fields for which the values/codes used by PrognoCIS and
the other applications will differ. For example, the default sex of a patient is
M in PrognoCIS, and the valid values are M and F, whereas in other applications,
the default could be Unknown and the valid values Unknown, Male, and Female. Hence,
we need to create a mapping set for each of the fields that need to be
imported. Which fields require mapping will be specified in the import
properties file. Code: A code for the mapping set to be created. Name: A name for the mapping set to be created. Ext Data Type: Select the field data type in the import file from the List Box. Our Data Type: Select the PrognoCIS field data type from the List Box. Ext Data Length: Enter the field length in the import file. Our Data Length: Enter the field length in PrognoCIS. Ext Data Default: The default value in the external application. (Used only for export) Our Data Default: The default value in PrognoCIS. Mapping Table: Enter the set of values in the external application, each mapped to the equivalent values in PrognoCIS. |