MirthResults is a complex piece of software. Sooner or later, you're going to need help configuring it or addressing an error.
Configuration Questions
Configuration issues can vary quite a bit. It all depends on the specific use case that MR is being used for. The most important thing is to be able to describe your needs.
- What actors (users, organizations, systems) are involved?
- What is the desired goal or outcome?
- What configuration steps have you already performed?
Messaging Errors
- What type of messages are you sending? HL7? CCD? MirthModels?
- Do you have a sample message available? Note that you should NOT send us messages containing protected health information!
- If the message format supports validation (CCD) is the message valid?
- What interface tools are being used to send the messages? MirthConnect? Were any errors logged in those interfaces?
- Are you running on an appliance or on your own installation? If on your own install, please locate the file server.log.
- Do these errors happen for every message? Some messages?
User Interface Errors
- What were you trying to do when the error happened?
- What user were you logged in as?
- What error message did you get?
Where is server.log?
If you are running MirthResults on a Mirth appliance, support will be able to help you get connected to SupportNet and gather the information.
If you are running MirthResults on your own installation, server.log should be located in the path defined by $AS_LOGS. Be sure and have this file handy when you contact support.
Labels: