HL7 FAC Facility
HL7 field reference FAC fields from HL7 v2.5.1 Show fields
These are the generated fields for the version selected at the top of the page. The document stays the same, but the reference panel follows that version.
Fields
| Field | Name | Required | Repeatable | Type | Table |
|---|---|---|---|---|---|
| FAC.1 | Facility ID-FAC | Yes | No | EI | |
| FAC.2 | Facility Type | No | No | ID | 0331 |
| FAC.3 | Facility Address | Yes | Yes | XAD | |
| FAC.4 | Facility Telecommunication | Yes | No | XTN | |
| FAC.5 | Contact Person | No | Yes | XCN | |
| FAC.6 | Contact Title | No | Yes | ST | |
| FAC.7 | Contact Address | No | Yes | XAD | |
| FAC.8 | Contact Telecommunication | No | Yes | XTN | |
| FAC.9 | Signature Authority | Yes | Yes | XCN | |
| FAC.10 | Signature Authority Title | No | No | ST | |
| FAC.11 | Signature Authority Address | No | Yes | XAD | |
| FAC.12 | Signature Authority Telecommunication | No | No | XTN |
FAC describes a facility record, including identifiers, names, contact details, and service attributes.
Master-file segments update reference data rather than describing a single patient event. They define locations, staff, providers, test catalogs, charge items, inventory items, languages, certificates, and other shared records.
Because many downstream messages depend on this data, small changes here can have large effects. Use stable identifiers, effective dates, action codes, and clear ownership rules instead of treating a master-file feed like a loose spreadsheet export.
The v2.5.1 structures show FAC in SUR_P09 - SUR - Summary product experience report. That tells you where it can appear, but the implementation guide still decides which optional fields are meaningful.
For practical interface work, read the generated field panel for datatype, required, repeatable, and table details, then use the notes below to decide what the field should mean in the receiving workflow.
FAC-1 identifies the Facility ID-FAC for this master-file record. Send the identifier that the receiving system actually keys on, and keep the assigning authority or coding system visible when the datatype supports it.
FAC-2 qualifies the master-file record rather than identifying it. This is the sort of field receivers often use for branching, filtering, or display grouping.
Use the agreed value set, starting from HL7 table 0331. A local code without an agreed coding system is a small ambiguity that becomes a mapping problem later.
FAC-3 carries contact details. Use the datatype components for use code, equipment type, address type, country, and other qualifiers rather than squeezing everything into one formatted string.
This field can repeat. Use repetitions for separate real-world values, not as a workaround for putting several unrelated ideas in one field.
FAC-4 carries contact details. Use the datatype components for use code, equipment type, address type, country, and other qualifiers rather than squeezing everything into one formatted string.
FAC-5 identifies a person, provider, staff member, or contact involved in this master-file record. Use the structured name or provider datatype instead of flattening everything into display text.
When more than one person is sent, repeats should carry role or identifier context so the receiver can tell who did what.
FAC-6 identifies a person, provider, staff member, or contact involved in this master-file record. Use the structured name or provider datatype instead of flattening everything into display text.
When more than one person is sent, repeats should carry role or identifier context so the receiver can tell who did what.
FAC-7 carries contact details. Use the datatype components for use code, equipment type, address type, country, and other qualifiers rather than squeezing everything into one formatted string.
This field can repeat. Use repetitions for separate real-world values, not as a workaround for putting several unrelated ideas in one field.
FAC-8 carries contact details. Use the datatype components for use code, equipment type, address type, country, and other qualifiers rather than squeezing everything into one formatted string.
This field can repeat. Use repetitions for separate real-world values, not as a workaround for putting several unrelated ideas in one field.
FAC-9 carries Signature Authority for this master-file record. Populate it only when the receiver has a clear use for it, and keep the value in the datatype shape shown in the generated field panel.
This field can repeat. Use repetitions for separate real-world values, not as a workaround for putting several unrelated ideas in one field.
FAC-10 carries Signature Authority Title for this master-file record. Populate it only when the receiver has a clear use for it, and keep the value in the datatype shape shown in the generated field panel.
FAC-11 carries contact details. Use the datatype components for use code, equipment type, address type, country, and other qualifiers rather than squeezing everything into one formatted string.
This field can repeat. Use repetitions for separate real-world values, not as a workaround for putting several unrelated ideas in one field.
FAC-12 carries contact details. Use the datatype components for use code, equipment type, address type, country, and other qualifiers rather than squeezing everything into one formatted string.