FHIR 中文版

本页内容:

数据类型
示例
详细描述
映射
1.17.1 数据类型的示例
这一部分包含了如下数据类型的示例

1.17.1 基本数据类型

布尔值：

1	<active value="true" />

负整数：

1	<score value="-14" />

高精度的小数：

1	<pi value="3.14159265358979323846264338327950288419716939937510" />

base64编码的字节流：

1	<data value="/9j/4...KAP//Z" /> <!-- covers many lines -->

unicode编码的字符串：

1	<caption value="Noodles are called ?? in Chinese" />

表示网站地址的uri:

1	<reference value="http://hl7.org/fhir" />

urn格式的uri:

1	<id value="urn:isbn:0451450523" />

出生日期:

1	<date value="1951-06-04" />

出生年月:

1	<date value="1951-06" />

临床文档创建的时间，包括时区:

1	<instant value="2013-06-08T10:57:34+01:00" />

精确到毫秒的UTC格式的临床文档创建时间:

1	<instant value="2013-06-08T09:57:34.2112Z" />

下午2点35分:

1	<time value="14:35" />

1.17.1.2 String Patterns

表示HL7的根oid的uri：

1	<root value="urn:oid:2.16.840.1.113883" />

uuid格式的uri:

1	<id value="urn:uuid:a5afddf4-e880-459b-876e-e4591b0acc11" />

A code:

1	<code value="acq4+acq5" />

带单空格的code:

1	<code value="Question 4b" />

数字型id:

1	<id value="314" />

字母型id:

1	<id value="alpha-gamma-14" />

1.17.1.3 Attachment

PDF文档:

1	<document> <contentType value="application/pdf" /> <language value="en" /> <data value="/9j/4...KAP//Z" /> <!-- covers many lines --> <title value="Definition of Procedure" /> </document>

1	document : { contentType : { value : "application/pdf" }, language : { value : "en" }, data : { value : "/9j/4...KAP//Z"}, title : { value : "Definition of Procedure" } }

WADO协议的DICOM图像:

1	<image> <contentType value="application/dicom" /> <url value="http://10.1.2.3:1000/wado?requestType=WADO&wado_details..." /> <hash value="EQH/..AgME" /> </image>

1.17.1.4 Identifier

Examples

系统主键:

1	<identifier> <use value="official" /> <system value="urn:oid:2.16.840.1.113883.16.4.3.2.5" /> <value value="123" /> </identifier> `

院内的病人编号:

1	<identifier> <use value="official" /> <system value="http://www.acmehosp.com/patients" /> <value value="44552" /> <period> <start value="2003-05-03" /> </period> </identifier> `

In this case, the period is used to track when the identifier was first assigned to the patient.

FHIR服务器中的患者标识:

1	<identifier> <system value="urn:ietf:rfc:3986" /> <value value="http://pas-server/xxx/Patient/443556" /> </identifier>

This is not a resource reference - it’s a logical reference by the patient identifier.

A UUID:

1	<identifier> <use value="temp" /> <system value="urn:ietf:rfc:3986" /> <value value="urn:uuid:a76d9bbf-f293-4fb7-ad4c-2851cac77162" /> </identifier> `

UUIDs are often used for temporary identifiers, though this is not necessary.

A US SSN:

1	<identifier> <use value="usual" /> <label value="SSN" /> <system value="http://hl7.org/fhir/sid/us-ssn" /> <value value="000111111" /> </identifier> `

Notes:

US SSNs are often presented like this: 000-11-1111, the dashes are for presentation and should be removed, as specified in the definition of ssn-us
The use of "usual" means that this institution prefers to use SSN when identifying the patient
(如果医院使用身份证号来标识患者是否也是usual;如果院内有自己唯一的主索引，身份证号是用usual还是official)

表单编号或病案号:

1	<identifier> <use value="usual" /> <label value="MRN" /> <system value="urn:oid:0.1.2.3.4.5.6.7" /> <value value="2356" /> <period> <start value="2009-07-05" /> </period> </identifier> `

1.17.1.5 Coding

Examples

头痛的ICD-10编码:

1	<code> <system value="http://hl7.org/fhir/sid/icd-10" /> <code value="G44.1" /> </code> `

A SNOMED CT expression:

1	<problem> <system value="http://snomed.info/sct" /> <code value="128045006:{363698007=56459004}" /> </problem>

1.17.1.6 CodeableConcept

Examples

SNOMED-CT编码的头痛，转换成ICD-10编码:

  <concept>
    <coding>
      <system value="http://hl7.org/fhir/sid/icd-10" />
      <code value="R51" />
    </coding>
    <coding>
      <system value="http://snomed.info/sct" />
      <code value="25064002" />
      <display value="Headache" />
      <primary value="true" />
    </coding>
    <text value="general headache" />
  </concept>
`

本地编码的剂型单位，UCUM中找不到对应编码:

1	<unit> <coding> <system value="urn:oid:2.16.840.1.113883.19.5.2" /> <code value="tab" /> <display value="Tablet" /> </coding> <coding> <system value="http://unitsofmeasure.org" /> </coding> </unit>

A SNOMED CT expression(由于该SNOMED-CT表达式不存在display，所以没有display元素):

1	<diagnosis> <coding> <system value="http://snomed.info/sct" /> <code value="128045006:{363698007=56459004}" /> </coding> <text value="Cellulitis of the foot" /> </diagnosis> `

Using the valueset:

The results on a urinalysis strip:

1	<valueCoding> <system value="http://example.org/codes/simple-grades" /> <code value="+" /> <valueSet> <reference url="ValueSet/simple-grades" /> </valueSet> </valueCoding> `

具体定义编码的value set如下所示:

<ValueSet xmlns="http://hl7.org/fhir">
  <text>
    <status value="generated"/>
    <div xmlns="http://www.w3.org/1999/xhtml">
      <p>Possible Clinistix codes: neg, trace, +, ++, and +++</p>
    </div>
  </text>
  <identifier value="http://hl7.org/fhir/vs/clinistix"/>
  <name value="Codes for Clinistix"/>
  <publisher value="HL7"/>
  <telecom>
    <system value="url"/>
    <value value="http://hl7.org/fhir"/>
  </telecom>
  <description value="Clinistix Codes"/>
  <status value="draft"/>
  <experimental value="true"/>
  <date value="2013-10-01"/>
  <define>
    <system value="http://hl7.org/fhir/clinistix"/>
    <caseSensitive value="false"/>
    <concept>
      <code value="neg"/>
    </concept>
    <concept>
      <code value="trace"/>
    </concept>
    <concept>
      <code value="+"/>
    </concept>
    <concept>
      <code value="+"/>
    </concept>
    <concept>
      <code value="++"/>
    </concept>
    <concept>
      <code value="+++"/>
    </concept>
  </define>
</ValueSet>

1.17.1.7 Quantity

Examples

A duration:

1	<time> <value value="25" /> <units value="sec" /> <system value="http://unitsofmeasure.org" /> <code value="s" /> </time> `

浓度超出范围:

1	<result> <value value="40000" /> <comparator value=">" /> <units value="mcg/L" /> <system value="http://unitsofmeasure.org" /> <code value="ug" /> </result> `

处方药的数量:

1	<dose> <value value="3" /> <units value="capsules" /> <system value="http://snomed.info/sct" /> <code value="385049006" /> </dose> `

A price (coded using currency codes defined in ISO 4217):

1	<cost> <value value="25.45" /> <units value="US$" /> <system value="urn:std:iso:4217" /> <code value="USD" /> </cost> `

1.17.1.8 Range

Examples

Range of Quantity (distance):

1	<estimate> <low> <value value="1.6" /> <units value="m" /> </low> <high> <value value="1.9" /> <units value="m" /> </high> </estimate> `

1.17.1.9 Ratio

Examples

滴速 (Ratio of integer:integer)

1	<result> <numerator> <value value="1" /> </numerator> <denominator> <value value="128" /> </denominator> </result> `

单位成本(Ratio of
Money:Quantity):



  <charge>
   <numerator>
     <value value="103.50" />
     <units value="US$" />
     <code value="USD" />
     <system value="urn:std:iso:4217" />
   </numerator>
   <denominator>
     <value value="1" />
     <units value="day" />
     <code value="day" />
     <system value="http://unitsofmeasure.org" />
   </denominator>
  </charge>

`

1.17.1.10 Period

Examples

2011年5月23到27 包括27号:

1	<coverage> <start value="2011-05-23" /> <end value="2011-05-27" /> </coverage> `

1.17.1.11 SampledData

Example

EKG设备的输出:

 <sampledData>
  <origin>
   <value value="0"/>
   <units value="μV"/>
   <system value="http://unitsofmeasure.org"/>
   <code value="uV"/>
  </origin>
  <period value="2"/>
  <factor value="2.5"/>
  <dimensions value="1"/>
  <data value="-4 -13 -18 -18 -18 -17 -16 -16 -16 -16 -16 -17 -18 -18 -18 ...."/>
 </sampledData>
`

1.17.1.12 HumanName

A Simple example

1	<name> <family value="Everyman" /> <given value="Adam" /> <given value="A." /> </name> `

Composite names

1	<name> <family value="Contrata" /> <given value="Mary Jane" /> </name> `

These cases can be quite ambiguous - is "Mary Jane" one name, or two? Different systems,
and data enterers may treat this differently, and the person themselves may not know.
Parts are allowed to contain spaces, but systems should consider how to treat
these cases. Composite names separated by "-" should be treated as a single name part.

A common pattern: a person is called by a name other than that expected from their official name (first given name in most cultures).

<name>
  <use value="official" />
  <family value="Chalmers" />
  <given value="Peter" />
  <given value="James" />
</name>
<name>
  <use value="usual" />
  <given value="Jim" />
</name>

This same pattern is often encountered with immigrants, who retain their real name for official use, but adopt a localized name for everyday use:

<name>
  <use value="official" />
  <family value="Sczypinski" />
  <given value="Piotr" />
  <given value="Andre" />
</name>
<name>
  <use value="usual" />
  <family value="Skipper" />
  <given value="Jim" />
</name>

Karen van Hentenryck is of Dutch origin, and the "van" is a voorvoegsel.

<name>
  <use value="official" />
  <family value="van">
    <extension url="http://hl7.org/fhir/StructureDefinition/iso21090-EN-qualifier" >
       <valueCode value="VV" />
    </extension>
  </family>
  <family value="Hentenryck" />
  <given value="Karen" />
</name>

See the Extensibility Example for more information.
Note that this name has multiple family name parts. Systems that do not support as many name parts
as are provided in an instance they are processing may wish to append parts together using spaces,
so that this becomes "van Hentenryck".

Complex example from Germany: Dr.phil. Regina Johanna Maria Gräfin Hochheim-Weilenfels, NCFSA. This example shows extensive use of
multiple given names, prefixes, suffixes, for academic degrees, nobility titles, and professional designations.

<name>
  <use value="official" />
  <family value="Hochheim-Weilenfels" />
  <given value="Regina" />
  <given value="Johanna" />
  <given value="Maria" />
  <prefix value="Gräfin">
    <extension url="http://hl7.org/fhir/StructureDefinition/iso21090-EN-qualifier" >
      <valueCode value="NB" />
    </extension>
  </prefix>
  <prefix value="Dr. phil.">
    <extension url="http://hl7.org/fhir/StructureDefinition/iso21090-EN-qualifier" >
      <valueCode value="AC" />
    </extension>
  </prefix>
  <suffix value="NCFSA" />
</name>
<name>
  <use value="maiden" />
  <family value="Hochheim" />
</name>

This example makes use of the ISO 21090 extensions to carry the rare ISO 21090 qualifier attributes "AC" and "NB".

Japanese example in the three forms: ideographic (Kanji), syllabic (Hiragana) and alphabetic (Romaji).

<name>
  <family value="??" />
  <given value="??" />
  </name>
<name>
 <family value="???" />
 <given value="???" />
</name>
<name>
  <family value="KIMURA" />
  <given value="MICHIO" />
</name>

The three forms are differentiated by the character subset each contains.

Russian example in the two forms: cyrillic, and latin:

<name>
  <family value="??????" />
  <given value="????" />
  <given value="????????????" />
</name>
<name>
  <family value="EMELIN" />
  <given value="IVAN" />
  <given value="VLADIMIROVICH" />
</name>

In Russian usage, these names are known as
the domestic and foreign names respectively. The two forms are differentiated by the character subset each contains.

Scandinavian example: Erikson is the family name. Jan Erik are the given names, and Östlund the family name of the mother, which is taken as a Mellannamn.

<name>
  <use value="official" />
  <family value="Erikson" />
  <given value="Jan" />
  <given value="Erik" />
  <given value="Östlund">
    <extension url="http://hl7.org/fhir/StructureDefinitioniso-20190#name-qualifier" >
      <valueCoding>
         <code value="MID" />
         <system value="http://hl7.org/fhir/v3/EntityNamePartQualifier2" />
      </valueCoding>
    </extension>
  </given>
</name>

This example makes use of the ISO 21090 extension to carry the culture specific ISO 21090 qualifier attribute "MID" for the Mellannamn.

Then Jan Erikson has a daughter, Karin, with his wife Margrete Hansen. The first communications of the new born
name is "Margrete Jente" (Margrete’s Girl) and the mother’s family name, not the given name (Karin). The
father’s Family name is not used at all. This is a known temporary name assigned directly after the birth of
the child.

<name>
  <use value="temp" />
  <!-- use could be OR+OLD, depends how record keeping is done -->
  <family value="Hansen" />
  <given value="Margrete Jente" />
</name>

The baby’s name is subsequently changed to the fathers’ family name, and to use the mother’s name as
mellomnamn.

<name>
  <use value="official" />
  <family value="Erikson" />
  <given value="Karin" />
  <given value="Hansen">
    <extension url="http://hl7.org/fhir/StructureDefinitioniso-20190#name-qualifier" >
      <valueCoding>
         <code value="MID" />
         <system value="http://hl7.org/fhir/v3/EntityNamePartQualifier2" />
      </valueCoding>
    </extension>
  </given>
</name>

Later, Karin gets married to Per Berg, and decides to adopts Berg as her family name, and also decides to use
Erikson as the mellom navn. (Note: Karin could have chosen to use another mellom navn, e.g. the family name of
her mother, her father or other family names as specified by naming laws of the country in question).

<name>
  <use value="old" />
  <family value="Erikson" />
  <given value="Karin" />
  <given value="Hansen">
    <extension url="http://hl7.org/fhir/StructureDefinitioniso-20190#name-qualifier" >
      <valueCoding>
        <code value="MID" />
        <system value="http://hl7.org/fhir/v3/EntityNamePartQualifier2" />
      </valueCoding>
    </extension>
  </given>
</name>
<name>
  <use value="official" />
  <family value="Berg" />
  <given value="Karin" />
  <given value="Erikson">
    <extension url="http://hl7.org/fhir/StructureDefinitioniso-20190#name-qualifier" >
      <valueCoding>
        <code value="MID" />
        <system value="http://hl7.org/fhir/v3/EntityNamePartQualifier2" />
      </valueCoding>
    </extension>
  </given>
</name>
<name>
  <use value="usual" />
  <family value="Berg" />
  <given value="Karin" />
</name>

#### 1.17.1.12.1 W3C International Examples These examples are taken from the [W3C International Examples](http://www.w3.org/International/questions/qa-personal-names), which should be consulted for further information. A patronymic is "The part of a name that links to the genealogy":

<name>
  <text value="Björk Guðmundsdóttir"/>
  <family value="Guðmundsdóttir"/>
  <given value="Björk"/>
</name>

A patronymic with a "son/daughter of" appellation:

<name>
  <text value="Isa bin Osman"/>
  <family value="bin Osman"/>
  <given value="Isa"/>
</name>

Note: The family name may also be given as two different family names.

A Chinese name with a generational name:

<name>
  <text value="???"/> <!-- left to right -->
  <family value="?"/>
  <given value="?"/>
  <given value="?"/>
</name>
<name>
  <text value="Mao Ze Dong"/> <!-- left to right -->
  <family value="Mao"/>
  <given value="Ze"/>
  <given value="Dong"/>
</name>

Todo: is there a need to identify the given name that is the generational name.

Additional Western name (see also example above):

<name>
  <use value="official" />
  <family value="Yao" />
  <given value="Ming" />
</name>
<name>
  <use value="usual" />
  <given value="Fred" />
</name>

Multiple Family names:

<name>
  <family value="Carreño" />
  <family value="Quiñones" />
  <given value="María-Jose" />
</name>

Brazilian Example:

<name>
  <family value="Eduardo" />
  <family value="Santos" />
  <family value="Tavares" />
  <family value="Melo" />
  <family value="Silva" />
  <given value="José" />
</name>

Russian Examples (using Cyrillic):

<name>
  <family value="??????????" />
  <family value="??????" />
  <given value="?????" />
</name>
<name>
  <family value="?????????" />
  <family value="???????" />
  <given value="?????" />
</name>

Example with Initial:

<name>
  <family value="Public" />
  <given value="John" />
  <given value="Q." />
</name>

Other Examples:

<name>
  <text value="Velikkakathu Sankaran Achuthanandan"/>
  <family value="Velikkakathu" />
  <given value="Sankaran" />
  <given value="Achuthanandan" />
</name>
<name>
  <text value="Kogaddu Birappa Timappa Nair"/>
  <family value="Nair" />
  <given value="Birappa" />
  <given value="Timappa" />
  <prefix value="Kogaddu" />
</name>
<name>
  <text value="Aditya Pratap Singh Chauhan"/>
  <family value="Singh" />
  <given value="Aditya" />
  <given value="Pratap" />
  <suffix value="Chauhan" />
</name>
<name>
  <text value="Madurai Mani Iyer"/>
  <given value="Mani" />
  <prefix value="Madurai" />
  <suffix value="Iyer" />
</name>
<name>
  <text value="Abu Karim Muhammad al-Jamil ibn Nidal ibn Abdulaziz al-Filistini"/>
  <family value="ibn Nidal" />
  <family value="ibn Abdulaziz" />
  <given value="Muhammad" />
  <given value="al-Jamil" />
  <prefix value="Abu Karim" />
  <suffix value="al-Filistini" />
</name>

Todo: need to discuss this with Indian / Arabic implementers.
Note that collecting and storing the text element makes the
primary purpose of the structured parts for index/searching, and
fidelity of the name parts is not critical.

1.17.1.13

Address

Example

HL7 office’s address.

  <address>
   <use value="work" />
   <text value="1050 W Wishard Blvd
RG
         5th floor
Indianapolis, IN 46240" />
   <line value="1050 W Wishard Blvd" />
   <line value="RG 5th floor" />
   <city value="Indianapolis" />
   <state value="IN" />
   <postalCode value="46240" />
  </address>

A UK example address.

  <address>
    <extension url="http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-county" > <!-- todo: review this -->
      <valueString value="HUDDERSFIELD"/>
    </extension>
    <text value="1 Back Lane&#13;&#10;Holmfirth&#13;&#10;HUDDERSFIELD&#13;&#10;HD7 1HQ"/>
    <line value="1 Back Lane"/>
    <city value="Holmfirth"/>
    <postalCode value="HD7 1HQ"/>
  </address>

A Postal address - i.e. an address that it doesn’t make sense to try and visit.

  <address>
    <extension url="http://hl7.org/fhir/StructureDefinition/iso21090-AD-use"> <!-- todo: review this -->
      <valueCode value="PST"/>
    </extension>
    <line value="PO Box 31445"/>
    <city value="Erewhon"/>
    <postalCode value="0001"/>
  </address>

#### 1.17.1.14 ContactPoint See also [Base Definition](datatypes.html#ContactPoint), [Detailed Descriptions](datatypes-definitions.html#ContactPoint) and [Mappings](datatypes-mappings.html#ContactPoint). **Example** Home phone number:

  <telecom>
   <system value="phone" />
   <value value="+15556755745" />
   <use value="home" />
  </telecom>

如果是微信二维码的话，如何标识： #### 1.17.1.15 Timing See also [Base Definition](datatypes.html#Timing), [Detailed Descriptions](datatypes-definitions.html#Timing) and [Mappings](datatypes-mappings.html#Timing). **Example** 预约了一个疗程的放疗？:

  <schedule>
    <event>
      <start value="2012-01-07T09:00:00+10:00" />
      <end value="2012-01-07T13:00:00+10:00" />
    </event>
    <event>
      <start value="2012-01-14T09:00:00+10:00" />
      <end value="2012-01-14T13:00:00+10:00" />
    </event>
    <event>
      <start value="2012-01-22T11:00:00+10:00" />
      <end value="2012-01-22T15:00:00+10:00" />
    </event>
  </schedule>
`

一天两次BID (twice a day) (no start or end specified):

1	<schedule> <repeat> <frequency value="2" /> <duration value="1" /> <units value="d" /> </repeat> </schedule> `

早饭前半小时，从2011年12月23开始连续十天 1/2 an hour before breakfast for 10 days from 23-Dec 2011:

1	<schedule> <event> <start value="2011-12-23" /> </event> <repeat> <when value="ACM" /> <duration value="30" /> <units value="min" /> <end value="2012-01-02" /> </repeat> </schedule> `

Note that the end date is inclusive like the high date of a Period. ### 1.17.1.16 Signature See also [Base Definition](datatypes.html#Signature), [Detailed Descriptions](datatypes-definitions.html#Signature) and [Mappings](datatypes-mappings.html#Signature). **Example** todo

  <signature>
    <!-- todo -->
  </signature>

FHIR 中文版

1.17.1 数据类型的示例

1.17.1 基本数据类型

1.17.1.2 String Patterns

1.17.1.3 Attachment

1.17.1.4 Identifier

1.17.1.5 Coding

1.17.1.6 CodeableConcept

1.17.1.7 Quantity

1.17.1.8 Range

1.17.1.9 Ratio

1.17.1.10 Period

1.17.1.11 SampledData

1.17.1.12 HumanName

1.17.1.13