Access restriction

ARV conveys access restriction directives on patient data. It specifies what action to take (restrict or unrestrict), which data categories are affected, the applicable date range, security classification tags, and a tracking identifier. It appears in ADT and other messages to enforce privacy policies.

Set the action code to restrict and the value to the data category:

from zato.hl7v2.v2_9 import ARV, CNE, CWE

arv = ARV()
arv.access_restriction_action_code = CNE(
    identifier='RS',
    text='Restrict',
    name_of_coding_system='HL70206'
)
arv.access_restriction_value = CWE(
    identifier='DEM',
    text='Demographics',
    name_of_coding_system='HL70717'
)

The access_restriction_date_range field uses the DR datatype:

from zato.hl7v2.v2_9 import ARV, DR

arv = ARV()
arv.access_restriction_date_range = DR(
    range_start_date_time='20240101',
    range_end_date_time='20241231'
)

The security_classification_tag field uses CWE with HL7 table 0952:

from zato.hl7v2.v2_9 import ARV, CWE

arv = ARV()
arv.security_classification_tag = CWE(
    identifier='V',
    text='Very restricted',
    name_of_coding_system='HL70952'
)

Use the access_restriction_instance_identifier field with the EI datatype:

from zato.hl7v2.v2_9 import ARV, EI

arv = ARV()
arv.access_restriction_instance_identifier = EI(
    entity_identifier='ARV-2024-001',
    namespace_id='MAIN'
)

Zato connects to any system that speaks HL7v2 over MLLP or FHIR over REST. This includes Epic, Cerner, Meditech, Allscripts, and other EHR platforms.

Yes, Zato has built-in MLLP support for sending and receiving HL7v2 messages. MLLP channels handle the framing protocol automatically.

Zato supports HL7 v2.9, which is backward compatible with earlier versions including v2.3, v2.5, and v2.7. Standard segments and datatypes are available as typed Python classes.

Yes. Zato handles both HL7v2 and FHIR natively, so you can parse v2 messages and build FHIR resources with IG-specific extensions in the same service. Typed Python classes are available for both protocols, including extensions from US Core, UK Core, Da Vinci, and other Implementation Guides.