Name Flags Card. Type Description & Constraints Encounter 0..* JP_Encounter 入院、外来情報 id S 0..1 string このリソースのID text S 0..1 Narrative このリソースの概要 status S 1..1 code generated | extensions | additional | empty Fixed Value: generated div S 1..1 xhtml このリソースの概要 status S 1..1 code このリソース状態 class S 1..1 Coding このリソースの分類 subject S 0..1 Reference(JP Core Patient Profile | Group) 患者の参照 reference S 0..1 string 患者の参照 period S 0..1 Period 入院、通院期間 start S 0..1 dateTime 入院、通院開始日 end S 0..1 dateTime 入院、通院終了日 serviceProvider S 0..1 Reference(JP Core Organization Profile) 医療機関の参照 reference S 0..1 string 医療機関の参照 Documentation for this format
実装ガイド作成：小山内 尚、西山 喜樹、能崎 克行
入院、外来を記録した情報です。 医療サービスの提供者と患者の間を繋ぐ情報を示します。
If the resource is contained in another resource, it SHALL NOT contain nested Resources
not(parent::f:contained and f:contained)
If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource
contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().as(canonical) | %resource.descendants().as(uri) | %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(canonical) = '#').exists()).not()).trace('unmatched', id).empty()
not(exists(for $id in f:contained/*/f:id/@value return $contained[not(parent::*/descendant::f:reference/@value=concat('#', $contained/*/id/@value) or descendant::f:reference[@value='#'])]))
If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated
contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()
not(exists(f:contained/*/f:meta/f:versionId)) and not(exists(f:contained/*/f:meta/f:lastUpdated))
If a resource is contained in another resource, it SHALL NOT have a security label
When a resource has no narrative, only systems that fully understand the data can display the resource to a human safely. Including a human readable representation in the resource makes for a much more robust eco-system and cheaper handling of resources by intermediary systems. Some ecosystems restrict distribution of resources to only those systems that do fully understand the resources, and as a consequence implementers may believe that the narrative is superfluous. However experience shows that such eco-systems often open up to new participants over time.
A resource should have narrative for robust management
The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.
All FHIR elements must have a @value or children
hasValue() or (children().count() > id.count())
A set of rules under which this content was created
A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc.
Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.
This element is labeled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation
The base language in which the resource is written.
Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute).
Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Extensions are always sliced by (at least) url
Additional content defined by implementations
May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Must have either extensions or value[x], not both
exists(f:extension)!=exists(f:*[starts-with(local-name(.), "value")])
generated | extensions | additional | empty
このリソースの概要がリソースのコンテンツから⽣成されたことを⽰す。
The contents of the html element are an XHTML fragment containing only the basic html formatting elements described in chapters 7-11 and 15 of the HTML 4.0 standard, elements (either name or href), images and internally contained stylesheets. The XHTML content SHALL NOT contain a head, a body, external stylesheet references, scripts, forms, base/link/xlink, frames, iframes and objects.
The narrative SHALL contain only the basic html formatting elements and attributes described in chapters 7-11 (except section 4 of chapter 9) and 15 of the HTML 4.0 standard, elements (either name or href), images and internally contained style attributes
not(descendant-or-self::*[not(local-name(.)=('a', 'abbr', 'acronym', 'b', 'big', 'blockquote', 'br', 'caption', 'cite', 'code', 'col', 'colgroup', 'dd', 'dfn', 'div', 'dl', 'dt', 'em', 'h1', 'h2', 'h3', 'h4', 'h5', 'h6', 'hr', 'i', 'img', 'li', 'ol', 'p', 'pre', 'q', 'samp', 'small', 'span', 'strong', 'sub', 'sup', 'table', 'tbody', 'td', 'tfoot', 'th', 'thead', 'tr', 'tt', 'ul', 'var'))]) and not(descendant-or-self::*/@*[not(name(.)=('abbr', 'accesskey', 'align', 'alt', 'axis', 'bgcolor', 'border', 'cellhalign', 'cellpadding', 'cellspacing', 'cellvalign', 'char', 'charoff', 'charset', 'cite', 'class', 'colspan', 'compact', 'coords', 'dir', 'frame', 'headers', 'height', 'href', 'hreflang', 'hspace', 'id', 'lang', 'longdesc', 'name', 'nowrap', 'rel', 'rev', 'rowspan', 'rules', 'scope', 'shape', 'span', 'src', 'start', 'style', 'summary', 'tabindex', 'title', 'type', 'valign', 'value', 'vspace', 'width'))])
The narrative SHALL have some non-whitespace content
descendant::text()[normalize-space(.)!=''] or descendant::h:img[@src]
These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope.
This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels.
May be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
May be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).
Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://hl7.org/fhir/R4/extensibility.html#modifierExtension).
Modifier extensions are expected to modify the meaning or interpretation of the resource that contains them
Identifier(s) by which this encounter is known / このEncounterが知られている識別子（複数可）
Identifier(s) by which this encounter is known. このEncounterが知られている識別子（複数可）。
This element is labeled as a modifier because it is a status element that contains status entered-in-error which means that the resource should not be treated as valid
No clear equivalent in HL7 v2; active/finished could be inferred from PV1-44, PV1-45, PV2-24; inactive could be inferred from PV2-16
List of past encounter statuses / 過去のEncouterのステータス一覧
The status history permits the encounter resource to contain the status history without needing to read through the historical versions of the resource, or even have the server store them. ステータス履歴(status History)は、リソースの歴史的なバージョンを読み込んだり、サーバーに保存させたりすることなく、Encouterリソースがステータス履歴を含むことを可能にする。
The current status is always found in the current version of the resource, not the status history. 現在のステータスは、ステータスの履歴ではなく、常にリソースの現在のバージョンにある。
Extensions that cannot be ignored even if unrecognized
May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).
Modifier extensions are expected to modify the meaning or interpretation of the element that contains them
planned | arrived | triaged | in-progress | onleave | finished | cancelled + / 予定｜到着｜トリアージ｜進行中｜保留中｜終了｜キャンセル+.
planned | arrived | triaged | in-progress | onleave | finished | cancelled +. 予定｜到着｜トリアージ｜進行中｜保留中｜終了｜キャンセル+.
Note that FHIR strings SHALL NOT exceed 1MB in size FHIR 文字列のサイズは 1MB を超えてはならないことに注意すること。
The time that the episode was in the specified status / そのエピソードが指定された状態になっていた時間。
The time that the episode was in the specified status. そのエピソードが指定された状態になっていた時間。
A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). Period is not used for a duration (a measure of elapsed time). See [Duration](http://hl7.org/fhir/R4/datatypes.html#Duration). これは期間ではない-これは時間の尺度（別のタイプ）であり、時間の固定値で発生する期間である。 期間は時間の範囲を指定する。 使用状況は、範囲全体が適用されるか（たとえば、「患者はこの時間範囲で入院していた」）、または範囲から1つの値が適用されるか（たとえば、「これら2回の間に患者に与える」）を指定する。 期間が必要な場合は、タイプをInterval | Durationとして指定する。
List of past encounter classes / 過去のEncouter classのリスト
The class history permits the tracking of the encounters transitions without needing to go through the resource history. This would be used for a case where an admission starts of as an emergency encounter, then transitions into an inpatient scenario. Doing this and not restarting a new encounter ensures that any lab/diagnostic results can more easily follow the patient and not require re-processing and not get lost or cancelled during a kind of discharge from emergency to inpatient. クラスの履歴は、リソースの履歴を経由することなく、Encouterの遷移を追跡することを可能にする。これは、入院患者が緊急時にEncouterした後、入院患者のシナリオに移行する場合に使用される。このようにして、新しいEncouterを再開しないようにすることで、検査/診断結果がより簡単に患者を追跡することができ、再処理を必要とせず、救急から入院への退院の際に紛失したりキャンセルされたりすることがないことを保証する。
inpatient | outpatient | ambulatory | emergency + / 入院｜外来｜外来｜救急＋
inpatient | outpatient | ambulatory | emergency +. 入院｜外来｜外来｜救急＋。
Codes may be defined very casually in enumerations or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. コードは列挙やコードリストの中で非常にカジュアルに定義されることもあれば、SNOMED CTのような非常にフォーマルな定義まである- 詳細はHL7 v3コア・プリンシプルを参照すること。
The time that the episode was in the specified class / 指定されたクラスにエピソードがあった時間
The time that the episode was in the specified class. 指定されたクラスにエピソードがあった時間。
Specific type of encounter / Encouterの具体的なタイプ
Specific type of encounter (e.g. e-mail consultation, surgical day-care, skilled nursing, rehabilitation). 具体的なEncouterの種類（メール相談、外科デイケア、熟練看護、リハビリテーションなど）
Since there are many ways to further classify encounters, this element is ..*. Encouterをさらに分類する方法はいろいろあるので、この要素は...*である。
Broad categorization of the service that is to be provided (e.g. cardiology). 提供されるサービスの大まかな分類（心臓病など）。
Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. すべてのターミノロジーの使用がこの一般的なパターンに適合するわけではない。場合によっては、モデルはCodeableConceptを使用せず、コーディングを直接使用して、テキスト、コーディング、翻訳、および要素間の関係とpre-coordinationとpost-coordinationの用語関係を管理するための独自の構造を提供する必要がある。
Broad categorization of the service that is to be provided.
Indicates the urgency of the encounter / このEncounterの緊急性を示す。
Indicates the urgency of the encounter. このEncounterの緊急性を示す。
While the encounter is always about the patient, the patient might not actually be known in all contexts of use, and there may be a group of patients that could be anonymous (such as in a group therapy for Alcoholics Anonymous - where the recording of the encounter could be used for billing on the number of people/staff and not important to the context of the specific patients) or alternately in veterinary care a herd of sheep receiving treatment (where the animals are not individually tracked). このEncounterは常に患者に関するものであるが、患者は実際にはすべての使用状況で知られているわけではなく、匿名である可能性のある患者のグループが存在する可能性がある。（匿名のアルコール依存症の集団療法など-遭遇は、人数/スタッフの請求に使用でき、特定の患者の状況には重要ではない）
Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
Type the reference refers to (e.g. "Patient")
The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent. The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources).
This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified.
Aa resource (or, for logical models, the URI of the logical model).
Logical reference, when literal reference is not known
An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.
When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
Plain text narrative that identifies the resource in addition to the resource reference.
This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
Episode(s) of care that this encounter should be recorded against / このEncounterが記録されるべきケアのエピソード
Where a specific encounter should be classified as a part of a specific episode(s) of care this field should be used. This association can facilitate grouping of related encounters together for a specific purpose, such as government reporting, issue tracking, association via a common problem. The association is recorded on the encounter as these are typically created after the episode of care and grouped on entry rather than editing the episode of care to append another encounter to it (the episode of care could span years). 特定のEncounterをケアの特定のエピソードの一部として分類する必要がある場合は、このフィールドを使用する必要がある。この関連付けにより、政府の報告、問題追跡、一般的な問題を介した関連付けなど、特定の目的のために関連するエンカウンターをグループ化することが容易になる。これらは通常、ケアのエピソードの後に​​作成され、ケアのエピソードを編集して別のエンカウンターを追加するのではなく、エントリ時にグループ化されるため、関連付けはエンカウンターに記録される（ケアのエピソードは数年にわたる場合がある）。
References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. 参照は、実際のFHIRリソースへの参照である必要があり、解決可能（内容に到達可能）である必要がある（アクセス制御、一時的な使用不可などを考慮に入れる）。解決は、URLから取得するか、リソースタイプによって該当する場合は、絶対参照を正規URLとして扱い、ローカルレジストリ/リポジトリで検索することによって行うことができる。
The ServiceRequest that initiated this encounter / このEncounterを開始したServiceRequest
The request this encounter satisfies (e.g. incoming referral or procedure request). このEncounterが満たすリクエスト（例：入ってくる紹介または手続きリクエスト）。
List of participants involved in the encounter / このEncounterに関わった参加者一覧
The list of people responsible for providing the service. サービスを提供する責任がある人々のリスト。
Role of participant in encounter / このエンカウンターにおける参加者の役割
Role of participant in encounter. このエンカウンターにおける参加者の役割。
The participant type indicates how an individual participates in an encounter. It includes non-practitioner participants, and for practitioners this is to describe the action type in the context of this encounter (e.g. Admitting Dr, Attending Dr, Translator, Consulting Dr). This is different to the practitioner roles which are functional roles, derived from terms of employment, education, licensing, etc. 参加者タイプは、個人がEncounterにどのように参加するかを示す。これには、開業医以外の参加者が含まれる。開業医の場合、これは、このEncounterのコンテキストでのアクションタイプを説明することである（例：入院医師、出席医師、翻訳者、コンサルティング医師）。これは、雇用、教育、ライセンスなどの条件から派生した機能的な役割である開業医の役割とは異なる。
Period of time during the encounter that the participant participated / この参加者が参加したEncounterの中での期間
The period of time that the specified participant participated in the encounter. These can overlap or be sub-sets of the overall encounter's period. 指定された参加者がEncounterに参加した期間。これらは重複することも、Encounter全体の期間のサブセットになることもある。
Persons involved in the encounter other than the patient / 患者以外のこのEncounterに関わった人
Persons involved in the encounter other than the patient. 患者以外のこのEncounterに関わった人。
The appointment that scheduled this encounter / このEncounterをスケジュールした予定
The appointment that scheduled this encounter. このEncounterをスケジュールした予定。
.outboundRelationship[typeCode=FLFS].target[classCode=ENC, moodCode=APT]
入院レセプトの場合、診療年月の1日または入院開始から診療最終日までの期間を入れます。 入院外レセプトの場合、診療年月の対象日を開始と終了に入れます。
入院レセプトの場合、入院年月日と診療年月の1日で新しいほうを開始日とします。
The high value includes any matching date/time. i.e. 2012-02-03T10:00:00 is in a period that has an end value of 2012-02-03.
If the end of the period is missing, it means that the period is ongoing
Quantity of time the encounter lasted (less time absent) / Encounterが続いた時間の量（欠席時間が少ない）
Quantity of time the encounter lasted. This excludes the time during leaves of absence. このエンカウンターが続いた時間。これは休職中の時間を除外する。
May differ from the time the Encounter.period lasted because of leave of absence. 休職のため、Encounter.periodが続いた時間とは異なる場合がある。
(PV1-45 less PV1-44) iff ( (PV1-44 not empty) and (PV1-45 not empty) ); units in minutes
Coded reason the encounter takes place / Encounterの発生をコード化された理由の情報
Reason the encounter takes place, expressed as a code. For admissions, this can be used for a coded admission diagnosis. 受診理由をコードで表現したもの。入院の場合はコード化された入院診断名に使用することができる。
For systems that need to know which was the primary diagnosis, these will be marked with the standard extension primaryDiagnosis (which is a sequence value rather than a flag, 1 = primary diagnosis). どれが主たる診断であったかを知る必要があるシステムでは、これらは標準のエクステンションであるprimaryDiagnosis（フラグではなくシーケンス値、1 = 主たる診断）でマークされる。
EVN-4 / PV2-3 (note: PV2-3 is nominally constrained to inpatient admissions; HL7 v2 makes no vocabulary suggestions for PV2-3; would not expect PV2 segment or PV2-3 to be in use in all implementations )
Reason the encounter takes place (reference) エンカウンターがあった理由
Reason the encounter takes place, expressed as a code. For admissions, this can be used for a coded admission diagnosis. コードとして表現されたエンカウンターが起こった理由。入院の場合、これはコード化されたコード化された入院時診断に使用できる。
The list of diagnosis relevant to this encounter / このEncounterに関連する診断名のリスト
The list of diagnosis relevant to this encounter. このEncounterに関連する診断名のリスト
The diagnosis or procedure relevant to the encounter / Encounterに関連する診断または処置
Reason the encounter takes place, as specified using information from another resource. For admissions, this is the admission diagnosis. The indication will typically be a Condition (with other resources referenced in the evidence.detail), or a Procedure. 受診理由（他のリソースからの情報を使用して指定されたもの）。入院の場合、これは入院診断名である。表現方法は通常、状態（evidence.detailで参照されている他のリソースを使用）、または処置である。
For systems that need to know which was the primary diagnosis, these will be marked with the standard extension primaryDiagnosis (which is a sequence value rather than a flag, 1 = primary diagnosis). どちらが一次診断であったかを知る必要があるシステムでは、これらは標準のエクステンションであるprimaryDiagnosis（フラグではなくシーケンス値、1 = 一次診断）でマークされる。
Resources that would commonly referenced at Encounter.indication would be Condition and/or Procedure. These most closely align with DG1/PRB and PR1 respectively.
Role that this diagnosis has within the encounter (e.g. admission, billing, discharge …) / この診断名がある受診機会において持っている役割（例えば、入院、請求、退院...）
Role that this diagnosis has within the encounter (e.g. admission, billing, discharge …). この診断名がある受診機会において持っている役割（例えば、入院、請求、退院...）。
The type of diagnosis this condition represents.
Ranking of the diagnosis (for each role type) / 診断名の順位（役割別）
Ranking of the diagnosis (for each role type). 診断名の順位（役割別）
The set of accounts that may be used for billing for this Encounter / あるEncounterの請求に使用される会計セット
The set of accounts that may be used for billing for this Encounter. あるEncounterの請求に使用される会計セット。
The billing system may choose to allocate billable items associated with the Encounter to different referenced Accounts based on internal business rules. 請求システムは、内部ルールに基づいて、ある受診機会に関連付けられた請求可能な項目を異なる参照先の会計に割り当てることができる。
Details about the admission to a healthcare service/医療機関への入院に関する詳細
Details about the admission to a healthcare service. 医療機関への入院に関する詳細
An Encounter may cover more than just the inpatient stay. Contexts such as outpatients, community clinics, and aged care facilities are also included. The duration recorded in the period of this encounter covers the entire scope of this hospitalization record. Encounterは、入院患者の滞在の記録だけではない。外来患者、地域の診療所、高齢者施設などのコンテクストも含まれる。 このEncouterの期間に記録された時間区間は、この入院記録の全範囲をカバーしている。
.outboundRelationship[typeCode=COMP].target[classCode=ENC, moodCode=EVN]
The location/organization from which the patient came before admission/患者が入院する前に来院した場所/組織
The location/organization from which the patient came before admission. 患者が入院する前に来院した場所/組織
References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. 参照は実際のFHIRリソースへの参照でなければならず、解決可能でなければならない。解決は URL からの検索、またはリソースタイプによって、絶対参照を正規の URL として扱い、ローカルのレジストリ/リポジトリで検索することで行うことができる。
From where patient was admitted (physician referral, transfer)/患者がどこから入院したか（医師の紹介、転院）
From where patient was admitted (physician referral, transfer). 患者がどこから入院したか（医師の紹介、転院） 例：他の病院からの転院、かかりつけ医からの紹介、この病院で産まれた、など
Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. すべての用語の使用がこの一般的なパターンに適合するわけではない。いくつかのケースでは、モデルはCodeableConceptを使用せず、Codingを直接使用し、テキスト、コーディング、翻訳、要素間の関係、および前後の調整を管理するための独自の構造を提供することが望ましい。
The type of hospital re-admission that has occurred (if any). If the value is absent, then this is not identified as a readmission / 発生した病院の再入院のタイプ（もしあれば）。値がない場合、これは再入院として識別されない。
Whether this hospitalization is a readmission and why if known. この入院が再入院であるかどうかと、わかっている場合はその理由。
The reason for re-admission of this hospitalization encounter.
Diet preferences reported by the patient / 患者から報告された食事の好み
Diet preferences reported by the patient. 患者から報告された食事の好み
For example, a patient may request both a dairy-free and nut-free diet preference (not mutually exclusive). 例えば、患者は、乳製品を含まない食事とナッツ類を含まない食事の両方を希望することができる（相互に排他的ではない）。
Used to track patient's diet restrictions and/or preference. For a complete description of the nutrition needs of a patient during their stay, one should use the nutritionOrder resource which links to Encounter. 患者の食事制限および／または好み・嗜好を追跡するために使用される。滞在中の患者の栄養ニーズの完全な説明については、EncounterにリンクしているnutritionOrderリソースを使用する必要がある。
Medical, cultural or ethical food preferences to help with catering requirements.
.outboundRelationship[typeCode=COMP].target[classCode=SBADM, moodCode=EVN, code="diet"]
Special courtesies (VIP, board member) / 特別待遇(VIP、役員)
Special courtesies (VIP, board member). 特別待遇(VIP、役員)
Wheelchair, translator, stretcher, etc. / 車椅子、トランスレーター、ストレッチャーなど
Any special requests that have been made for this hospitalization encounter, such as the provision of specific equipment or other things. 特定の器具の提供など、今回の入院の出会いのために特別な要望があったもの
Location/organization to which the patient is discharged / 患者が退院する場所・機関
Location/organization to which the patient is discharged. 患者が退院する場所・機関
Category or kind of location after discharge / 退院後の場所の区分や種類。
Category or kind of location after discharge. 退院後の場所の区分や種類。
List of locations where the patient has been / 患者がいたことのある場所の一覧
List of locations where the patient has been during this encounter. このEncounterの間に患者がいたことのある場所のリスト
Virtual encounters can be recorded in the Encounter by specifying a location reference to a location of type "kind" such as "client's home" and an encounter.class = "virtual". 仮想Encouterは、"client's home "のような "kind "型の場所を参照し、encounter.class = "virtual "を指定することで、Encounterに記録することができる。
Location the encounter takes place / Encounterの場所
The location where the encounter takes place. Encounterの舞台となる場所。
The status of the participants' presence at the specified location during the period specified. If the participant is no longer at the location, then the period will have an end date/time. 指定された期間中の指定された場所での参加者の存在状況。参加者がその場所にいなくなった場合、その期間は終了日時を持つ。
When the patient is no longer active at a location, then the period end date is entered, and the status may be changed to completed. 患者がその場所で活動しなくなった場合、期間終了日が入力され、ステータスが完了した状態に変更されることがある
The physical type of the location (usually the level in the location hierachy - bed room ward etc.) / 場所の物理的なタイプ（通常は場所の階層のレベル - ベッド・病室・病棟など）
This will be used to specify the required levels (bed/ward/room/etc.) desired to be recorded to simplify either messaging or query. これは、メッセージングまたはクエリのいずれかを簡素化するために記録したい必要なレベル（ベッド/ワード/ルーム/その他）を指定するために使用される。
This information is de-normalized from the Location resource to support the easier understanding of the encounter resource and processing in messaging or query. There may be many levels in the hierachy, and this may only pic specific levels that are required for a specific usage scenario. この情報は、メッセージングやクエリでのEncouterリソースの理解や処理を容易にするために、Locationリソースから非正規化されている。 階層には多くのレベルがあり、これは特定の使用シナリオに必要とされる特定のレベルのみをピックすることができる。
Time period during which the patient was present at the location / 患者がその場所にいた期間
Time period during which the patient was present at the location. その場所に患者がいた期間。
A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). Period is not used for a duration (a measure of elapsed time). See [Duration](http://hl7.org/fhir/R4/datatypes.html#Duration). 期間は時間の範囲を指定する。 使用のコンテキストは、範囲全体が適用されるかどうかを指定する (例: "患者はこの時間範囲の病院の入院患者でした" )。または、範囲から1つの値が適用される（例：「この2回の間に患者に与える」）。 期間は、期間(経過時間の尺度)には使用されない。Duration](http://hl7.org/fhir/R4/datatypes.html#Duration)を参照のこと。
Another Encounter this encounter is part of / このEncouterが属するもう一つのEncouter
Another Encounter of which this encounter is a part of (administratively or in time). このEncouterが（管理的に、あるいは時間的に）一部となっているもう一つのEncouter。
This is also used for associating a child's encounter back to the mother's encounter. Refer to the Notes section in the Patient resource for further details. 子供の受診を母親の受診にさかのぼって連携するときにも使われる。 （※出産時などを表していると思われる） 詳細については、Patient ResourceのNotesセクションを参照のこと。
.inboundRelationship[typeCode=COMP].source[classCode=COMP, moodCode=EVN]