The Healthcare: Medical devices to EMR pattern can optionally query a database for patient identifiers. Patient identification is important so that device measurements are associated with the correct patient. The database associates device identifiers with patient identifiers. The device identifiers are propagated in the messages from the MedicalDeviceInput Node. The patient identifier is added by the pattern instance to the HL7 v2 observation result messages (ORU R01) sent to the destination application.
You need a database with one table and an ODBC definition to lookup patient identifiers. To access the database the broker must be configured with a user identifier and password.
Complete the following tasks to setup the database tables:
Follow the instructions that are relevant to your database manager:
Complete the following tasks to setup the database environment for the broker:
Use the mqsisetdbparms command to specify a user identifier and password that the broker can use with the PATIENTSDSN data source. This user identifier must be the same user identifier that you used when you created the database in the previous step. The user identifier determines the database schema name, and the broker must use the same user identifier when accessing the table. For example, if your user identifier is USERID , the fully-qualified name of the PATSDB table name is USERID.PATSDB .
mqsisetdbparms BROKERNAME -n PATIENTSDSN -u <user ID> -p <password>
mqsireload BROKERNAME -e EXECUTIONGROUPNAME
Back to the Healthcare: Medical devices to EMR pattern specification