Secure Messaging: Sending Letters via Healthlink & Medical Objects

MediRecords enables secure electronic correspondence with health professionals using trusted messaging providers such as Healthlink and Medical Objects. This ensures sensitive patient information is shared safely, quickly, and in line with industry standards.

Before sending correspondence, your practice must be registered with one of these providers, and contacts must be validated as users of Healthlink or Medical Objects. This article explains the prerequisites, configuration steps, how to validate contacts, and how to send letters via secure messaging.

For more detailed technical guidance, see Secure Messaging Configuration Guide.

Contents

1. Pre-Requisites for Sending Letters via Secure Messaging
2. Practice Configuration
3. Validating Contacts for Secure Messaging
4. Sending Letters via Secure Messaging
5. Medical Objects Provider Number Requirements
6. Understanding Secure Messaging Statuses
7. Further Reading

Pre-Requisites for Sending Letters via Secure Messaging

Before sending letters via secure messaging:

• Your practice must be registered with Healthlink or Medical Objects.
• Your practice configuration must include valid secure messaging credentials.
• The sender must have a valid Provider Number in MediRecords (mandatory for Medical Objects).
• The recipient contact must be validated as a secure messaging user.
• For Medical Objects: The sender must also be registered in the Medical Objects network.

Practice Configuration

1. Go to More.
2. Click Settings.
3. Choose the Configuration Settings tile.
    
4. Choose the practice.
    
5. Under Secure Messaging, enter the details provided by your vendor:
   • Healthlink (HL): EDI address (e.g., menopagp)

   • Medical Objects (MO): URL and Name Space format:

     ℹ️ https://hd-.moc.medical-objects.com.au/hl7/ Name Space: Practice Name^GUID^GUID
6. Click Save.

Validating Contacts for Secure Messaging

Once Secure Messaging is configured:

1. Click More on the MediRecords menu ribbon, select Resources, and click Contacts.
    
2. Choose Health Professionals.
    
3. Use the search filter to locate the contact and click their Name.
    
4. Ensure a Provider Number is entered.
    
5. Select the Secure Messaging Provider (Healthlink or Medical Objects).
    

6. Click Validate.
   
    

   ℹ️ Note: MediRecords sends a request to confirm the contact’s active status in the provider directory.
   If successful, a toast message appears, and you can hover over the info icon to view:
   • Last Validation Date
   • EDI (for Healthlink)
   • Medical Objects Provider Number

Sending Letters via Secure Messaging

1. Open the Patient Record, go to the Clinical section, and click the New Letter icon.
    
2. Search for the contact by name, select it, and click Save.
    
3. Click Letter, choose the type, and select the template.
    
4. Make any necessary edits, then click File and Save.
    
5. Enter the Subject and any additional details, and then click Save and Send.

ℹ️ Note: The letter will be sent and appear in your Secure Messaging Outbox.
To view it, click the Secure Messaging Icon on the menu ribbon, then select Outbox.

✅ Tip: If successful, you'll receive a green toast message - “Outbound message sent”.

Medical Objects Provider Number Requirements

If your practice is configured with Medical Objects, the sender of the letter must have a valid Provider Number.

• If the sender’s Provider Number is missing or invalid, the message will still be delivered to the recipient.
• However, the system will not be able to retrieve the delivery acknowledgment report, and the message status will remain as Pending.

To avoid this, please ensure that all users have entered their correct Provider Number in the User Profile, under the Identifiers section.

Understanding Secure Messaging Statuses

Secure Messaging letters can show the following statuses:

• Pending: Message has been sent, but no delivery acknowledgment has been received.
• Delivered: Message has been successfully delivered and acknowledged by the recipient’s system.
• Failed: Message could not be delivered due to configuration issues or incorrect recipient details.

Further Reading

• Secure Messaging Configuration Guide
• Secure Messaging FAQs