Announcement

Collapse
No announcement yet.

File Writer won't work with FHIR DSTU2

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • File Writer won't work with FHIR DSTU2

    Hi,

    Beating my head against the floor on this... I wanted to parse data elements from a FHIR message and so figured it would be easier to do my testing by writing data to a file. I set up the File Writer on my destination transformer and can't get it to create a file. I see the data being written to the Postgre DB and I am getting 200 OK messages in my Rest Client, no errors on anything, the file just doesn't get written to a folder on my local hard drive.

    Using the FHIR listener and example Channel from Tech Preview 2 on Mirth Connect 3.3.1.7856 and Java 1.8.66 on a Windows 2008 R2 box. I have another Channel that reads data from an HL7 2.5 file, parses it and writes text to the same folder on this box just fine but my FHIR channel using the FHIR listener won't create the file. I have even tried creating the file with raw text and built in Destination Mappings like the Channel ID and/or Channel Name, no joy. Nothing spits out a file. No errors, nothing in Windows Event viewer. It is like the File Writer destination is being skipped and doesn't fire when a message is received.

    I can post the channel if helpful...
    Mark Beans
    http://MedicalSoftwareTools.com

  • #2
    Here is my channel...

    Here is my channel...
    Attached Files
    Mark Beans
    http://MedicalSoftwareTools.com

    Comment


    • #3
      As noted in the wiki page, the source transformer uses destination set filtering to determine which destinations to send a message to. You can tweak that code so that it doesn't remove the File Writer from the destination set.
      Step 1: JAVA CACHE...DID YOU CLEAR ...wait, ding dong the witch is dead?

      Nicholas Rupley
      Work: 949-237-6069
      Always include what Mirth Connect version you're working with. Also include (if applicable) the code you're using and full stacktraces for errors (use CODE tags). Posting your entire channel is helpful as well; make sure to scrub any PHI/passwords first.


      - How do I foo?
      - You just bar.

      Comment


      • #4
        Big help!

        Thanks Nick, BIG help! Sorry I didn't get that first time round.

        Mark
        Mark Beans
        http://MedicalSoftwareTools.com

        Comment

        Working...
        X