# encounter Kunjungan pasien dapat didefinisikan sebagai interaksi pasien terhadap suatu layanan Fasyankes. Sebagai contoh, dalam satu rangkaian rawat jalan, seluruh rangkaian dapat didefinisikan sebagai satu “Encounter”. Data-data kunjungan pasien yang direkam meliputi kapan pertemuan tersebut mulai dan selesai, siapa tenaga kesehatan yang melayani, siapa subjek dari pelayanannya, dan informasi pendukung lainnya. ## \*e**ncounter.identifier** Berisi satu atau lebih daftar data mengenai informasi terkait kode atau nomor kunjungan yang dimiliki oleh lokasi induk yang setiap datanya direpresentasikan dengan tipe data Identifier.

Elemen	Nilai Elemen
Encounter.identifier[i].use	Berisi data dengan tipe data `code`, yang nilainya mengacu pada data terminologi IdentifierUse.
Encounter.identifier[i].system	http://sys-ids.kemkes.go.id/encounter/{organization-ihs-number} dengan `{organization-ihs-number}` adalah ID organisasi induk yang didapatkan dari master sarana indeks.
Encounter.identifier[i].value	Berisi kode atau ID lokal/nomor kunjungan lokal yang disimpan di sistem internal masing-masing organisasi.

### Encounter.identifier\[i].use

Code	Display	Definition
usual	Usual	The identifier recommended for display and use in real-world interactions which should be used when such identifier is different from the "official" identifier.
official	Official	The identifier considered to be most trusted for the identification of this item. Sometimes also known as "primary" and "main". The determination of "official" is subjective and implementation guides often provide additional guidelines for use.
temp	Temp	A temporary identifier.
secondary	Secondary	An identifier that was assigned in secondary use - it serves to identify the object in a relative context, but cannot be consistently assigned to the same object again in a different context.
old	Old	The identifier id no longer considered valid, but may be relevant for search purposes. E.g. Changes to identifier schemes, account merges, etc.

### **Contoh** e**ncounter.identifier** {% code title="Contoh encounter.identifier" overflow="wrap" %} ```json [ { "system": "http://sys-ids.kemkes.go.id/encounter/10000004", "use": "official", "value": "P20240001" } ] ``` {% endcode %} ## **\*encounter.status** Berisi data status tahapan dari kunjungan pasien dengan tipe data code, yang nilainya mengacu pada data terminologi EncounterStatus ().

Code	Display	Definition
planned	Planned	The Encounter has not yet started.
in-progress	In Progress	The Encounter has begun and the patient is present / the practitioner and the patient are meeting.
on-hold	On Hold	The Encounter has begun, but is currently on hold, e.g. because the patient is temporarily on leave.
discharged	Discharged	The Encounter has been clinically completed, the patient has been discharged from the facility or the visit has ended, and the patient may have departed (refer to subjectStatus). While the encounter is in this status, administrative activities are usually performed, collating all required documentation and charge information before being released for billing, at which point the status will move to completed.
completed	Completed	The Encounter has ended.
cancelled	Cancelled	The Encounter has ended before it has begun.
discontinued	Discontinued	The Encounter has started, but was not able to be completed. Further action may need to be performed, such as rescheduling appointments related to this encounter.
entered-in-error	Entered in Error	This instance should not have been part of this patient's medical record.
unknown	Unknown	The encounter status is unknown. Note that "unknown" is a value of last resort and every attempt should be made to provide a meaningful value other than "unknown".

### **\*Encounter.statusHistory** | Elemen | Nilai Elemen | | ------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Encounter.statusHistory.status | Berisi satu atau lebih data penyimpanan riwayat status dari kunjungan pasien dengan tipe data code. Terdapat 3 status yang wajib dikirimkan datanya yaitu arrived, In-progress, dan finished, yang nilainya mengacu pada data terminologi EncounterStatus (). | | Encounter.statusHistory.period | Berisi satu atau lebih data penyimpanan waktu/log dari kunjungan pasien dengan tipe data `Period`. | ### **\*Encounter.statusHistory.status**

Code	Display	Definition
planned	Planned	The Encounter has not yet started.
in-progress	In Progress	The Encounter has begun and the patient is present / the practitioner and the patient are meeting.
on-hold	On Hold	The Encounter has begun, but is currently on hold, e.g. because the patient is temporarily on leave.
discharged	Discharged	The Encounter has been clinically completed, the patient has been discharged from the facility or the visit has ended, and the patient may have departed (refer to subjectStatus). While the encounter is in this status, administrative activities are usually performed, collating all required documentation and charge information before being released for billing, at which point the status will move to completed.
completed	Completed	The Encounter has ended.
cancelled	Cancelled	The Encounter has ended before it has begun.
discontinued	Discontinued	The Encounter has started, but was not able to be completed. Further action may need to be performed, such as rescheduling appointments related to this encounter.
entered-in-error	Entered in Error	This instance should not have been part of this patient's medical record.
unknown	Unknown	The encounter status is unknown. Note that "unknown" is a value of last resort and every attempt should be made to provide a meaningful value other than "unknown".

### \*Encounter.statusHistory.period

Elemen	Nilai Elemen
*Encounter.statusHistory.period.start	Diisi dengan waktu mulai, sama dengan waktu dimulainya suatu status kunjungan dalam format `YYYY-MM-DD`. Contoh: `"2022-06-14T07:00:00+07:00"`
*Encounter.statusHistory.period.end	Diisi dengan waktu mulai, sama dengan waktu berakhirnya suatu status kunjungan dalam format `YYYY-MM-DD`. Contoh: `"2022-06-14T07:00:00+07:00"`

## encounter.class Berisi data klasifikasi dari pertemuan pasien dengan tipe data `Coding`, yang nilainya mengacu pada salah satu data terminologi dengan nama [ActEncounterCode](http://terminology.hl7.org/CodeSystem/v3-ActCode).

Elemen	Nilai Elemen
Encounter.class.system	"http://terminology.hl7.org/CodeSystem/v3-ActCode"
Encounter.class.code	Berisi kode sesuai jenis kunjungan.
Encounter.class.display	Berisi kode atau ID lokal/nomor kunjungan lokal yang disimpan di sistem internal masing-masing organisasi.

### Encounter.class.code & Encounter.class.display

Code	Display	Definition
AMB	ambulatory	A comprehensive term for health care provided in a healthcare facility (e.g. a practitioneraTMs office, clinic setting, or hospital) on a nonresident basis. The term ambulatory usually implies that the patient has come to the location and is not assigned to a bed. Sometimes referred to as an outpatient encounter.
EMER	emergency	A patient encounter that takes place at a dedicated healthcare service delivery location where the patient receives immediate evaluation and treatment, provided until the patient can be discharged or responsibility for the patient's care is transferred elsewhere (for example, the patient could be admitted as an inpatient or transferred to another facility.)
FLD	field	A patient encounter that takes place both outside a dedicated service delivery location and outside a patient's residence. Example locations might include an accident site and at a supermarket.
HH	home health	Healthcare encounter that takes place in the residence of the patient or a designee
IMP	inpatient encounter	A patient encounter where a patient is admitted by a hospital or equivalent facility, assigned to a location where patients generally stay at least overnight and provided with room, board, and continuous nursing service.
ACUTE	inpatient acute	An acute inpatient encounter.
NONAC	inpatient non-acute	Any category of inpatient encounter except 'acute'
OBSENC	observation encounter	An encounter where the patient usually will start in different encounter, such as one in the emergency department (EMER) but then transition to this type of encounter because they require a significant period of treatment and monitoring to determine whether or not their condition warrants an inpatient admission or discharge. In the majority of cases the decision about admission or discharge will occur within a time period determined by local, regional or national regulation, often between 24 and 48 hours.
PRENC	pre-admission	A patient encounter where patient is scheduled or planned to receive service delivery in the future, and the patient is given a pre-admission account number. When the patient comes back for subsequent service, the pre-admission encounter is selected and is encapsulated into the service registration, and a new account number is generated. Usage Note: This is intended to be used in advance of encounter types such as ambulatory, inpatient encounter, virtual, etc.
SS	short stay	An encounter where the patient is admitted to a health care facility for a predetermined length of time, usually less than 24 hours.
VR	virtual	A patient encounter where the patient and the practitioner(s) are not in the same physical location. Examples include telephone conference, email exchange, robotic surgery, and televideo conference.

## encounter.identifier

--- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://dokumentasisatusehat-stg.dto.kemkes.go.id/resource-and-terminologi/daftar-resources-and-terminologi/encounter.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.

Encounter.identifier[i].use

*Encounter.statusHistory.period.start

Encounter.class.system