Practitioner org unit

ORG defines organizational units within healthcare organizations. It's used to structure departments, clinics, facilities, and practice groups, particularly useful for organizing wellness center services.

Use HL70464 table values for unit types like DEPT (Department), CLINIC (Clinic), or FAC (Facility):

org.organization_unit_type = CWE(
    identifier='DEPT',
    text='Department',
    name_of_coding_system='HL70464'
)

organization_unit_identifier identifies the specific unit with codes and IDs, while organization_name contains the parent organization information. Both use XON datatype but serve different purposes.

Use multiple ORG segments to represent hierarchical structures. Each ORG can reference parent units through the organization_unit_identifier or establish relationships through the organization_name field.

Use HL70464 for organization unit types. For custom unit types, ensure consistent coding across your wellness center organization.

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.