Appearance
4.4 Human Readable Content
The human readable content is represented by a single MIME part. This MIME-part may contain a single representation of the human readable content or may contain multiple representations using the multi-part/alternative content type defined in Section 5.1.4 of RFC2046. The multi-part/alternative is used to supply alternative representation of the human readable content which the recipient system can choose the best fit for their use case.
MIME Part Elements for the Human Readable Content
| Data Element Number | Context Element | Value | Value Set | Context/Metadata Requirement |
|---|---|---|---|---|
| (2) | Content-Type | At least one representation of the human readable content SHALL use mimeType text/plain. If using multipart/alternative each MIME part of the multipart/alternative SHALL use an applicable MIME type corresponding to the human readable content representation. | Expected Value | R |
| (3) | Content-Transfer- Encoding | This is an optional field and the possible values are specified in section 6.1 of RFC2045. | O |
The MIME part for the human readable content SHALL NOT include a Content-Disposition of attachment. The intent for the human readable content is to have the content directly readable within an edge client. The human readable content appears in the message without taking additional action such as opening an attachment.
When the message includes an XDM attachment, the MIME part for the human readable message body SHALL be first.
CMS requires messages “convey, at a minimum, the patient’s basic personal or demographic information, as well as the name of the sending institution (that is, the hospital), and, if not prohibited by other applicable law, diagnosis.”
In order to ensure that any receiver of the Notification, regardless of their ability to process an HL7 V2.5.1 message or any other allowable attachment, this IG requires the following minimum data content be sent as a part of the body of the message:
| Data Element Number | Element Name | Content | Value Set | Requirement |
(15) or (38) | Notification Type | Context IG: activity-code XD: typeCode | D | R |
| (42) | Event Date/Time | EVN-2.1 - Recorded Date/Time-Time | Event Date/Time represents the date and time at the location where the event occurred. | R |
| (47-50) | Patient Name | PID-5 – Patient Name | R | |
| (52) | Patient DOB | PID-7 - Date/Time of Birth | R | |
| (53) | Patient Gender | PID-8 – Administrative Sex | A | R |
| (75) | Treating Facility | PV1-3.9 - Assigned Patient Location.Location Description | R | |
| (72) | Treating Facility Identifier (Type 2 NPI) | EVN-7.2 – Event Facility.Universal Id | ||
| (99) | Diagnosis | DG1-3.2* Diagnosis Code DG1.Text | RE | |
| (77) | Admission Type | PV1-4 – Admission Type | L | RE |
| (97) | Admission Reason | PV2-3 – Admit Reason | R when event type is admission. RE when event type is discharge/transfer | |
| (88) | Treating Provider (Admitting) NPI | PV1-17.1 – Admitting Doctor.Id Number | RE‡ | |
| (89) | Treating Provider (Admitting) Last Name | PV1-17.2 – Admitting Doctor.Family Name | RE‡ | |
| (90) | Treating Provider (Admitting) First Name | PV1-17.3 – Admitting Doctor.Id Number | RE‡ | |
| (92) | Treating Provider (Admitting) Direct address | ROL-12.4 - Phone.Email Address | RE‡ | |
| (79.A) | Treating Provider (Attending) NPI | PV1-7.1 – Attending Doctor.Id Number | RE‡ | |
| (79) | Treating Provider (Attending) Last Name | PV1-7.2 – Attending Doctor.Family Name | RE‡ | |
| (80) | Treating Provider (Attending) First Name | PV1-7.3 – Attending Doctor.Given Name | RE‡ | |
| (82) | Treating Provider (Attending) Direct address | ROL-12.4 - Phone.Email Address | RE‡ | |
| (83) | Treating Provider (Consulting) NPI | PV1-9.1 – Consulting Doctor.Id Number | RE‡ | |
| (84) | Treating Provider (Consulting) Last Name | PV1-9.2 – Consulting Doctor.Family Name | RE‡ | |
| (85) | Treating Provider (Consulting) First Name | PV1-9.3 – Consulting Doctor.Given Name | RE‡ | |
| (87) | Treating Provider (Consulting) Direct address | ROL-12.4 - Phone.Email Address | RE‡ |
‡ For Treating Provider, at least one of Attending, Consulting or Admitting Doctor is Required.
**