EncounterType

Reference data for healthcare encounter types following FHIR encounter classification. Categorizes encounters by care setting and typical characteristics for scheduling, billing, and reporting.

Overview

EncounterType provides standardized classification of healthcare visits. Each type has a code, label, FHIR class alignment, and typical duration. This enables consistent encounter categorization across systems, supports scheduling with appropriate time slots, and aligns with industry standards for interoperability.

Key Concepts

Type Structure

Each encounter type contains:

Field	Purpose	Example
`code`	Short identifier	AMB, EMER, IMP
`label`	Human-readable name	Ambulatory
`class`	FHIR encounter class	ambulatory
`typicalDurationMinutes`	Expected length	30
`description`	Additional details	Outpatient office visit

Standard Types

Common encounter types:

Code	Label	Class	Typical Duration
`AMB`	Ambulatory	ambulatory	30 minutes
`EMER`	Emergency	emergency	180 minutes
`IMP`	Inpatient	inpatient	Variable
`VR`	Virtual	virtual	20 minutes
`OBS`	Observation	observation	Up to 48 hours
`HH`	Home Health	home	Variable

FHIR Class Alignment

The class field aligns with FHIR ActEncounterCode:

Enables standard reporting
Supports data exchange
Consistent analytics
Regulatory compliance

Typical Duration

The typicalDurationMinutes field:

Guides scheduling systems
Default appointment length
Resource planning
May vary by specialty or facility

Use Cases

Appointment Scheduling

When booking visits:

Select appropriate encounter type
Use typical duration for time slot
Apply class for resource allocation
Display label to users
Support scheduling rules

Encounter Creation

When documenting visit:

Reference encounter type
Inherit class for reporting
Compare actual vs typical duration
Support billing workflows
Enable type-based analytics

Reporting and Analytics

For operational metrics:

Group encounters by type
Calculate volume by class
Compare duration to typical
Track type distribution
Support quality measures

System Configuration

For facility setup:

Define available encounter types
Set facility-specific durations
Map to billing codes
Configure scheduling rules
Align with organizational needs

Interoperability

For data exchange:

Map to FHIR encounter class
Support standard coding
Enable cross-system analytics
Meet regulatory requirements
Facilitate HIE participation

Related Entities

Entity	Relationship	Description
Encounter	Referenced by	Encounters of this type

Enums

class

Value	Description
`ambulatory`	Outpatient visit at clinic, office, or other ambulatory setting
`emergency`	Emergency department visit for urgent or emergent care
`inpatient`	Hospital admission requiring overnight stay
`observation`	Short-stay observation, typically less than 48 hours
`home`	Healthcare services delivered in patient's home
`virtual`	Telehealth, video visit, or remote care encounter
`other`	Other encounter type not classified above

5 properties

Schema

Properties

Property	Type	Mode	Description	Required
code	string	stored	Encounter type code Example: `"AMB"`	Required
label	string	stored	Human-readable name of the encounter type Example: `"Ambulatory"`	Required
class	string	stored	FHIR encounter class Values: `ambulatory, emergency, inpatient, observation, home, virtual, other` Example: `"ambulatory"`	Required
typicalDurationMinutes	number	stored	Typical duration of this encounter type in minutes Example: `30`	Optional
description	string	stored	Additional details about the encounter type	Optional

Examples

Example 1

{
  "@type": "EncounterType",
  "code": "AMB",
  "label": "Ambulatory",
  "class": "ambulatory",
  "typicalDurationMinutes": 30,
  "description": "Outpatient visit in a clinic or office setting"
}

Example 2

{
  "@type": "EncounterType",
  "code": "EMER",
  "label": "Emergency",
  "class": "emergency",
  "typicalDurationMinutes": 180,
  "description": "Emergency department visit"
}

Example 3

{
  "@type": "EncounterType",
  "code": "IMP",
  "label": "Inpatient",
  "class": "inpatient",
  "description": "Hospital admission for inpatient care"
}

Example 4

{
  "@type": "EncounterType",
  "code": "VR",
  "label": "Virtual",
  "class": "virtual",
  "typicalDurationMinutes": 20,
  "description": "Telehealth or video visit"
}