Common Data Models Harmonization
1.0.0 - STU 1 Publication

Common Data Models Harmonization, published by HL7 International - Biomedical Research and Regulation Work Group. This is not an authorized publication; it is the continuous build for version 1.0.0). This version is based on the current content of https://github.com/HL7/cdmh/ and changes regularly. See the Directory of published versions

ValueSet: PCORNet Encounter Type

Summary

Defining URL:http://hl7.org/fhir/us/cdmh/ValueSet/pcornet-encounter-type
Version:1.0.0
Name:PCORNetEncounterType
Title:PCORNet Encounter Type
Status:Active as of 9/6/21
Definition:

The PCORNet Encounter Type contains the codes to be used by PCORNet data marts.

Publisher:HL7 International - Biomedical Research and Regulation Work Group
Copyright:

Used by permission of HL7, all rights reserved Creative Commons License

Source Resource:XML / JSON / Turtle

References

Logical Definition (CLD)

 

Expansion

This value set contains 12 concepts

Expansion based on PCORNet Encounter Type Codes v1.0.0 (CodeSystem)

All codes in this table are from the system http://hl7.org/fhir/us/cdmh/CodeSystem/pcornet-encounter-type-codes

CodeDisplayDefinition
AVAmbulatory VisitIncludes visits at outpatient clinics, physician offices, same day/ambulatory surgery centers, urgent care facilities, and other same-day ambulatory hospital encounters, but excludes emergency department encounters.
EDEmergency DepartmentIncludes ED encounters that become inpatient stays (in which case inpatient stays would be a separate encounter). Excludes urgent care facility visits. ED claims should be pulled before hospitalization claims to ensure that ED with subsequent admission won't be rolled up in the hospital event. Does not include observation stays, where known.
EIEmergency Department Admit to Inpatient Hospital Stay (permissible substitution)Permissible substitution for preferred state of separate ED and IP records. Only for use with data sources where the individual records for ED and IP cannot be distinguished.
IPInpatient Hospital StayIncludes all inpatient stays, including: same-day hospital discharges, hospital transfers, and acute hospital care where the discharge is after the admission date. Does not include observation stays, where known.
ISNon-Acute Institutional StayIncludes hospice, skilled nursing facility (SNF), rehab center, nursing home, residential, overnight non-hospital dialysis, and other non-hospital stays.
OSObservation StayHospital outpatient services given to help the doctor decide if the patient needs to be admitted as an inpatient or can be discharged. Observations services may be given in the emergency department or another area of the hospital.” Definition from Medicare, CMS Product No. 11435, https://www.medicare.gov/Pubs/pdf/11435.pdf.
ICInstitutional Professional Consult (permissible substitution)Permissible substitution when services provided by a medical professional cannot be combined with the given encounter record, such as a specialist consult in an inpatient setting; this situation can be common with claims data sources. This includes physician consults for patients during inpatient encounters that are not directly related to the cause of the admission (e.g. a ophthalmologist consult for a patient with diabetic ketoacidosis) (guidance updated in v4.0).
THTelehealthIncludes telemedicine or virtual visits, which can be conducted via video, phone or other means.
OAOther Ambulatory VisitPIncludes other non-overnight AV encounters such as hospice visits, home health visits, skilled nursing visits, other non-hospital visits, as well as telemedicine, telephone and email consultations. May also include 'lab only' visits (when a lab is ordered outside of a patient visit), 'pharmacy only' (e.g., when a patient has a refill ordered without a face-to-face visit), 'imaging only', etc.
NINo informationPatient Encounter Type has No information.
UNUnknownPatient Encounter Type is Unknown.
OTOtherPatient Encounter Type is Other.

Explanation of the columns that may appear on this page:

Level A few code lists that FHIR defines are hierarchical - each code is assigned a level. In this scheme, some codes are under other codes, and imply that the code they are under also applies
Source The source of the definition of the code (when the value set draws in codes defined elsewhere)
Code The code (used as the code in the resource instance)
Display The display (used in the display element of a Coding). If there is no display, implementers should not simply display the code, but map the concept into their application
Definition An explanation of the meaning of the concept
Comments Additional notes about how to use the code