Aug 22, 2017 · 2 min read
Abigail Watson Thanks for this post! It was immensely helpful, especially since you’ve included all the tools necessary to get started, including a FHIR server with test data and HAPI TestPanel tips.
I couldn’t get Part 2 Destination JSON to HL7 v2 to work. If anybody has tips or resources, please share.
Here are some tips for anybody else going through the full tutorial:
Mirth Connect
- Edit Transformer — Paste the example HL7 v2 message in ‘Inbound Message Template’ to take advantage of the ‘Message Trees’, which will help understand the JavaScript syntax more quickly
- Transformer debugging — It may help to open the Mirth Connect launcher twice — 1 to edit destination transformer, and 1 for dashboard to reprocess problematic messages
- JavaScript Logging: logger.info(“debug message” + msg);
Mirth Connect on Mac
- Mac may give you errors about log file write permission
- Try installing under ~/ or find . | xargs chmod as needed
- Default password is admin:admin
- Since port 80 requires sudo on Mac, try another port, ex) 8081
- Update settings.tutorial.json to port 8081, which determines where the ‘Send’ button sends to
- Key name is Meteor.settings.public.interfaces.default.channel.endpoint
Meteor-FHIR
- Meteor-FHIR default login is sysadmin@test.org:password — server/fixtures.js
- Turn on Simple Schema debug mode: set SimpleSchema.debug=true inside Meteor.startup — https://github.com/aldeed/meteor-simple-schema#debug-mode
Part 1
- Latest Meteor-on-FHIR uses STU3 https://github.com/clinical-meteor/hl7-resource-patient/blob/c517a97c6d5aa48aaaaee8aed9e7f8ec3c4268b4/lib/Patients.js#L351
- STU3 channel should look like this https://github.com/ihealthdavid/meteor-on-fhir/commit/5e60989bcf17287c16bae9a9efaf674449880e71#diff-163b85f7f597599d0bdf2cef9761604e
- Channel Destination HTTP Sender output ‘Content’ should be: ${message.transformedData} not $(message.transformedData) — You can just drag and drop from the ‘Destination Mappings’ window
- Content Type should be: application/json
Part 2
- TCP MLLP debugging: start with File Writer and tail -f the file
- Destination: If JSON to HL7 v2 doesn’t work, start with JSON to JSON or JSON to RAW
