194 | | Language is then mandatorily indicated in two places in the EHR data, namely in Compositions and Entries (i.e. Observations, etc), in a language attribute. This allows both Compositions of different languages in the EHR, and Entries of different languages in the same Composition. Additionally, within Entries, text and coded text items may optionally have language recorded if it is different from the language of the enclosing Entry, or where these types are used within other non-Entry structures that don't indicate language. |
195 | | |
196 | | The use of these features is mostly likely to occur due to translation, although in some cases a truly multi-lingual environment might exist within the clinical encounter context. In the former case, some parts of an EHR, e.g. particular Compositions will be translated before or after a clinical encounter to as to make the information available in the primary language of the EHR. The act of translation (like any other interaction with the EHR) will cause changes to the record, in the form of new Versions. New translations can conveniently be recorded as branch versions, attached to the version of which they are a translation. This is not mandatory, but provides a convenient way to store translations so that they don't appear to replace the original content. |
| 196 | 次に言語は強制的にEHRデータの二つの場所で指定される。つまり、CompositionとEntry(例えばObservationなど)のlanguage属性である。こうすることで、EHRで尾となる言語をCompositionで使うことができ、同じCompositionにある複数のエントリーで異なる言語を利用することができる。さらに、Entry内部でテキストやコード化されたテキストといった項目はEntry内部での言語と違うものであれば、その言語で記録することも出来、これらの型は言語を指定しなくてもよいEntry型以外の構造で使われることもある。[[BR]]Language is then mandatorily indicated in two places in the EHR data, namely in Compositions and Entries (i.e. Observations, etc), in a language attribute. This allows both Compositions of different languages in the EHR, and Entries of different languages in the same Composition. Additionally, within Entries, text and coded text items may optionally have language recorded if it is different from the language of the enclosing Entry, or where these types are used within other non-Entry structures that don't indicate language. |
| 197 | |
| 198 | 実際の多言語環境は、いくつかの場面において臨床で遭遇する内容ではあるが、これらの特徴は翻訳の時にもっともよく利用される。翻訳の場合にはEHRのある部分(例えば、特定のComposition)が臨床で起こることの前後でEHRの第一言語で利用できる情報に翻訳するために利用される。(他のEHRとの交流のような場面での)翻訳作業では記録を新しいVersionの形式に変更することもある。新しい翻訳はバージョンのブランチとして便利に記録することが出来、翻訳のバージョンを付け加えることができる。これは強制されるものではないが、大本の内容を置換することなく翻訳を記録する便利な方法を提供している。The use of these features is mostly likely to occur due to translation, although in some cases a truly multi-lingual environment might exist within the clinical encounter context. In the former case, some parts of an EHR, e.g. particular Compositions will be translated before or after a clinical encounter to as to make the information available in the primary language of the EHR. The act of translation (like any other interaction with the EHR) will cause changes to the record, in the form of new Versions. New translations can conveniently be recorded as branch versions, attached to the version of which they are a translation. This is not mandatory, but provides a convenient way to store translations so that they don't appear to replace the original content. |