Application Certification Requirements (For Message Validation Only)
Note: The requirements listed here only apply to Clinical message validation.
Directory Presentation
C.100 The participant’s application shall display, at a minimum, the following Provider data elements from the directory whenever browsing the directory or displaying directory search results.
- LastName
- FirstName
- ClinicName
- SpecialtyType1
C.101 The participant’s application shall be able to display, at a minimum, the following Provider data elements from the directory.
- PrefixName
- LastName
- FirstName
- MiddleName
- SuffixName
- ClinicName
- AddressLine1
- AddressLine2
- City
- State
- Zip
- PhonePrimary
- SpecialtyType1
Sending Messages
C.102 The participant’s application shall actively notify the end user when a message is not successfully sent to the recipient(s).
Examples of actively notifying the end user – A new message delivered to the end user, a flag on the message the notification relates to, a pop up box.
C.103 If the participant’s application allows the end user to set or modify the message’s subject line, the application shall display, without end user action, a disclaimer that Protected Health Information (PHI) under HIPAA must not be included in a message’s subject line.
Sample disclaimer – Note: subject text is not encrypted - do not include sensitive or private information.
C.104 If the participant systematically populates the message's subject line, Protected Health Information (PHI) under HIPAA must not be included in a message’s subject line.
C.105 If batching messages, the participant’s application shall wait a maximum of one minute between processes to send messages to the Surescripts network.
Receiving Messages
C.106 The participant’s application shall make the message available to the intended recipient(s) within one minute of receiving it.
C.107 The participant’s application shall be able to receive a message of at least 20 MB.
C.108 The participant’s application shall be able to display, at a minimum, the following from the message.
- Date/Time
- Sender (From)
- Subject
- Message Body (text/plain or text/html part)
C.109 The participant’s application shall be able to display, at a minimum, the following attachment types:
- HTML
- RTF
- TXT
- XML
C.110 The participant’s application shall, at a minimum, make all attachments regardless of type available to download unless the attachment type is filtered for security reasons.
C.111 If an attachment is filtered for security reasons, the participant’s application shall notify the recipient of the message the attachment was removed and the filename of the attachment.