Appointment location

AIL contains appointment location information including facility details, room numbers, building information, and location codes. It's used to specify where wellness appointments and preventive care visits will take place.

Use HL70464 table values for location types like ROOM, OFFICE, or STUDIO:

ail.ail_location_type = CWE(
    identifier='ROOM',
    text='Room',
    name_of_coding_system='HL70464'
)

Include specific room numbers, building names, floor information, or descriptive details that help patients and staff locate the appointment venue within the wellness center facility.

Use XON datatype to include both the organization name and a unique location identifier. This helps map appointments to specific rooms or facilities within the wellness center.

AIL provides location details while AIP provides location preference information. Both segments work together to specify where appointments should take place and any location-related requirements.

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.