1.11.1 サンプルデータ一覧

Home ＞ Documentation ＞ Data Types ＞ Examples [datatypes-examples]

Data Type Examples1.11.1

This page includes additional examples of the data types, based on common usages and questions

Primitive Types 1.11.1.1

String Patterns 1.11.1.2

Attachment 1.11.1.3

Identifier 1.11.1.4

Coding 1.11.1.5

CodeableConcept 1.11.1.6

Choice 1.11.1.7

Quantity 1.11.1.8

Range 1.11.1.9

A boolean true value:

A negative integer value:

A high-precision decimal value:

A stream of bytes, base64 encoded:

A unicode string:

A uri that points to a website:

A uri that is a urn:

A date of birth:

An approximate date of birth:

The instant a document was created, including timezone:

The instant a document was created, expressed in UTC, with milliseconds:

A uri that is the root oid of HL7:

A uri that is a uuid:

A code:

A code with single internal space:

A numeric id:

An alphanumeric id:

A PDF document:

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

Since the JSON examples have the same structure as the XML, only XML is shown for the rest of the examples.

A reference to a DICOM image via WADO:

Examples

A primary key from an application table (an OID in the space allocated by HL7 to some organization to further sub-allocate):

A patient identifier defined by a hospital:

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

An identifier that refers to a patient FHIR resource on a particular system:

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

A UUID:

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

A US SSN:

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

A medical record number assigned on 5-July 2009:

Examples

A simple code for headache, in ICD-10:

A SNOMED-CT expression:

Examples

A simple code for headache initially coded in SNOMED-CT and translated to ICD-10:

A concept represented in an institution's local coding systems for unit for which no UCUM equivalent exists:

A SNOMED-CT expression:

In this case, there is no display element, because no display is defined for Snomed-CT expressions.

Example

The results on a urinalysis strip:

Examples

A duration:

A concentration where the value was out of range:

An amount of prescribed medication:

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

Examples

Range of Quantity (distance):

Ratio 1.11.1.10

Period 1.11.1.11

SampledData 1.11.1.12

HumanName 1.11.1.13

Address 1.11.1.14

Contact 1.11.1.15

Schedule 1.11.1.16

Examples

Titer (Ratio of integer:integer)

Unit cost (Ratio of :Quantity):

Examples

23rd May 2011 to 27th May, including 27th May:

Example

The output from an EKG device:

A Simple example

Composite names

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).

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

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

See the Extensibility Example for more information

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.

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).

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

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

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.

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.

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

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).

Example

HL7 office's address.

Further examples

Example

Home phone number:

Example

A series of appointments for radiotherapy:

BID (twice a day) (no start or end specified):

1/2 an hour before breakfast for 10 days from 23-Dec 2011:

Note that the end date is inclusive like the high date of a Period.