Appendix 5 Conformance Statements (Normative)

Senders/Receivers

Orders

Order addressing - Senders and receivers must ensure an order message is addressed using MSH-6 Receiving facility, as per rules in sub points of HD Datatype conformance heading HL7au:00044.2.

Receivers

Orders

The system must actively reject an order message where the MSH-6 Receiving Facility does not identify their organisation

Senders

Orders

When using SMD refer to HL7au:000044.2 otherwise; senders should address order messages in MSH-6 Receiving facility using the NATA number if available.

Senders

Orders

In MSH-6 the namespace ID should contain the registered NATA name for the laboratory as published by NATA ( www.nata.com.au )

Receivers

Results, Referrals

The system receiving messages must ensure that any document identifiers (OBR-3 Filler order number (EI)) in the received message are fully specified, with the authoring organisation's HD qualifying the identifier. This is done by testing that all components of Entity Identifier (EI) are valued, and when not returning error acknowledgement.

Document updating depends on a reliable document identifier and without a namespace for the identifier safe updating/corrections to documents is not possible.

Senders

Orders, Results, Referrals

If OBR-2 is valued, then to ensure the uniqueness of the Entity Identifier (EI) in OBR-2 (Placer Order Number) for a request identifier across different organisations, the Entity identifier (first component) in addition to the Namespace ID (second component) and Universal ID (third component) and Universal ID type (4th component) must be populated.

field optionality is still allowed i.e. field may be completely unvalued

Senders

Orders, Results, Referrals

If OBR-3 is valued, then to ensure the uniqueness of the Entity Identifier (EI) in OBR-3 (Filler Order Number) for a result identifier across different organisations, the Entity identifier (first component) in addition to the Namespace ID (second component) and Universal ID (third component) and Universal ID type (4th component) must be populated.

It is vital that a unique identifier within the authoring facility HD is used in the first component. The ability to issue corrected documents depends on the uniqueness of this document identifier. Future updates to a document will use the same identifier in OBR-3.

Receivers

Orders, Results, Referral

Older results with identical Entity Identifier (EI) in OBR-3 (Filler Order Number) to that of a newly received result message (by comparing OBR-22 Rpt/Status Change Date/Time field) must be replaced with the new message, and the older marked as deleted/superseded.

This applies independently to each OBR/OBX group

Senders

Orders, Results, Referrals

If ORC-2 is valued, then to ensure the uniqueness of the Entity Identifier (EI) in ORC-2 (Placer Order Number) for a request identifier across different organisations, the Entity identifier (first component) in addition to the Namespace ID (second component) and Universal ID (third component) and Universal ID type (4th component) must be populated.

field optionality is still allowed i.e. field may be completely unvalued

Senders

Orders, Results

If ORC-3 is valued, then to ensure the uniqueness of the Entity Identifier (EI) in ORC-3 (Filler Order Number) for a result identifier across different organisations, the Entity identifier (first component) in addition to the Namespace ID (second component) and Universal ID (third component) and Universal ID type (4th component) must be populated.

Senders

Orders, Results, Referrals

If ORC-4 is valued, then to ensure the uniqueness of the Entity Identifier (EI) in ORC-4 (Placer Group Number) for a request identifier across different organisations, the Entity identifier (first component) in addition to the Namespace ID (second component) and Universal ID (third component) and Universal ID type (4th component) must be populated. 

field optionality is still allowed i.e. field may be completely unvalued

(HL7au:000008)

Display Segments

Senders

Results, Referrals

The message must contain at least one OBX display segment per OBR/OBX group.

**wording updated, same intention

Senders

Results, Referrals

Display segments must use the appropriate valid values within the AUSPDI coding system in OBX-3 for the content that is represented in it:

• OBX||ED|HTML^Display format in HTML^AUSPDI||^text^HTML^A^<?xml
  version="1.0"…

• OBX||ED|PDF^Display format in PDF^AUSPDI||^application^pdf^Base64^

• OBX||ED|RTF^Display format in RTF^AUSPDI||…

• OBX||FT|TXT^Display format in text^AUSPDI||…

(Referral Level 1 receivers are only required to support PDF display segments. See HL7au:000008.3.1)

Receivers

Results, Referrals

For Referrals Level 1

Receivers must be capable of displaying PDF (either via an embedded viewer or an external viewer)

For other profiles:

Receivers should be capable of displaying all display formats HTML, PDF, RTF, TXT (HL7 FT) (either via an embedded viewer or an external viewer), and must provide users access to all of these in an external viewer application if they are unable to fully display the format.

*This conformance point was relaxed 31/10/2017.

Some formats may be viewed with an embedded viewer and external viewer, while other formats may be viewed with just an external viewer e.g. RTF). It is important that all can be accessed and viewed.

Senders and Receivers

Results

An OBX display segment is identified using OBX-3 Identifier (CE-1) and Name of Coding System (CE-3) components. The text component of the CE may be blank and only CE1 and CE-3 components need to match.

Senders and Receivers

Results

In an OBX display segment, the OBX-2 Value Type field must match its corresponding display format specified in OBX-3 Identifier (ST) component as per table Display Format codes in Section 4.5 Display Segments.

Senders and Receivers

Results

In an OBX display segment, the OBX-3 <name of coding system (IS)> must be valued "AUSPDI".

Senders

Results, Referrals

The OBX display segment(s) must be the last in a set of OBX segments in each OBR/OBX group, with the exception of digital signature OBX(s) which may be after the display segments OBXs. (Display segments can be identified by having AUSPDI OBX-3 <name of coding system>)

Receivers

Results, Referrals

When a display segment is shown, the earlier atomic OBX segments must not be rendered.

Senders

Results

There must NOT be conflicting content between the OBX display segment and the preceding OBX atomic data. A compliant rendering of the atomic data (if present) must contain the same clinical information.

Senders

Referrals

For OBX within the supporting information OBR/OBX groups. There must NOT be conflicting content between the OBX display segment and the preceding OBX atomic data. A compliant rendering of the atomic data (if present) must contain the same clinical information.

Senders

Referrals

For OBX within the current summary OBR/OBX group as indicated by OBR-4 as per section 4.4.1.4.1 OBR-4 codes in referral messages. There must NOT be conflicting content between the OBX display segment and the preceding OBX atomic data and the medication and allergy segments of the REF message.

Senders

Referrals

For Referrals Level 1:

The single OBR/OBX group of the message must contain an OBX display segment in PDF format.

For other profiles:

Each OBR/OBX group of the message must contain at least one of the following OBX display segments HTML, PDF, TXT (HL7 FT).

Senders

Referrals(L2)

If an RTF display segment is sent in an OBR/OBX group, then the same content must be sent in one of either HTML, PDF, or TXT (HL7 FT) same OBR/OBX group.

XHTML Display Segment

XHTML Display Segment - Sender

Senders

Results, Referrals

Any OBX HTML display segments must be valid HTML and conform to the Document Type defined in 'XHTML 1.0 Strict' standard. Refer to  http://validator.w3.org/ to validate XHTML content.

Senders

Results, Referrals

All embedded hyperlinks must be secure hyperlinks i.e. https:// . That is http:// is disallowed.

Senders

Results, Referrals

Sender must not use external style sheets. Internal style sheets are allowed.

Note: external stylesheets are a security risk and could affect presentation of content.

Senders

Results, Referrals

Sender must not use scripts e.g. JavaScript etc.

Note: active content is not allowed either inline or as external references.

Senders

Results, Referrals

Sender must not use the following elements:

• base

• link

• xlink

• frame

• iframes

• form

• object

Senders

Results, Referrals

If there is an image map, senders must have an additional mechanism for communicating that information because there is no obligation on receiving systems to deal with image maps.

Senders

Results, Referrals

Embedded CSS shall conform to the CSS3 specification.

Senders

Results, Referrals

The core display of the report must be encapsulated in a 'div' element of html class ‘reportDisplay’.

Senders

Results, Referrals

Letter head information should be encapsulated in XHTML elements outside of the scope of the core display of the report identified by 'div' html class 'reportDisplay'.

Senders

Results, Referrals

Letter head images may not be embedded in the html but served externally.

Senders

Results, Referrals

External letter head image sources must not be used, except when used outside a 'div' 'reportDisplay' class html element and only when that 'div' it is present.

Senders

Results, Referrals

The core report must display in a readable way with the CSS removed.

Senders

Results, Referrals

Information in the core report data must not be hidden by CSS formatting directives. 

Senders

Results, Referrals

Image element "src" attributes must use the value "hl7v2://OBX.<setID>" where the setID reference the OBX in the message containing the Encapsulated Data (ED) image or Reference Pointer (RP) to the data, except for images which are a part of a letterhead as per HL7au:000008.2.3.1.10.

Senders

Results, Referrals

External images may be linked from the report body via a clickable link which the user can manually select.

e.g. to access a PACS image

XHTML Display segment - Receiver

Receivers

Results, Referrals(L2)

HTML display segments must be displayed using a HTML/CSS component that is compliant for rendering of XHTML and CSS3.

Receivers

Results, Referrals(L2)

Secure hyperlinks (https://) must be able to be clicked by a user and client application must enable navigation to secure https:// sites .

Receivers

Results, Referrals(L2)

Receiving software may filter or disable all embedded JavaScript.

Receivers