HL7 Terminology
1.0.0 - Publication
HL7 Terminology
1.0.0 - Publication
This page is part of the HL7 Terminology (v1.0.0: Release) based on FHIR R4. The current version which supercedes this version is 5.2.0. For a full list of available versions, see the Directory of published versions 
Source view
<CodeSystem xmlns="http://hl7.org/fhir"> <id value="v3-mediatypes"/> <language value="en"/> <text> <status value="generated"/> <div xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"><h2>Media Type</h2><div><p>Internet Assigned Numbers Authority (IANA) Mime Media Types. Identifies the type of the encapsulated data and identifies a method to interpret or render the data. The IANA defined domain of media types is established by the Internet standard RFC 2045 [http://www.ietf.org/rfc/rfc2045.txt] and 2046 [http://www.ietf.org/rfc/rfc2046.txt]. RFC 2046 defines the media type to consist of two parts:</p> <ol> <li>top level media type, and</li> <li>media subtype</li> </ol> <p>However, this HL7 datatypes specification treats the entire media type as one atomic code symbol in the form defined by IANA, i.e., top level type followed by a slash "/" followed by media subtype. Currently defined media types are registered in a database [http://www.iana.org/assignments/media-types/index.html] maintained by IANA. Currently several hundred different MIME media types are defined, with the list growing rapidly. In general, all those types defined by the IANA syntax MAY be used. This code system is a substet of all possible media type codes which are used in HL7 Standaards and Implementation Guides. More information and documentation of this content can be found at Multipurpose Internet Mail Extensions (MIME) Part Four - BCP 13. [http://tools.ietf.org/html/bcp13]</p> </div><p><b>Properties</b></p><table class="grid"><tr><td><b>Code</b></td><td><b>URL</b></td><td><b>Description</b></td><td><b>Type</b></td></tr><tr><td>Specializes</td><td/><td>The child code is a more narrow version of the concept represented by the parent code. I.e. Every child concept is also a valid parent concept. Used to allow determination of subsumption. Must be transitive, irreflexive, antisymmetric.</td><td>Coding</td></tr><tr><td>Generalizes</td><td/><td>Inverse of Specializes. Only included as a derived relationship.</td><td>Coding</td></tr><tr><td>internalId</td><td>http://terminology.hl7.org/CodeSystem/utg-concept-properties#v3-internal-id</td><td>The internal identifier for the concept in the HL7 Access database repository.</td><td>code</td></tr><tr><td>status</td><td>http://hl7.org/fhir/concept-properties#status</td><td>Designation of a concept's state. Normally is not populated unless the state is retired.</td><td>code</td></tr><tr><td>synonymCode</td><td>http://hl7.org/fhir/concept-properties#synonym</td><td>An additional concept code that was also attributed to a concept</td><td>code</td></tr></table><p>This code system http://terminology.hl7.org/CodeSystem/v3-mediatypes defines many codes, of which the following are a subset:</p><table class="codes"><tr><td><b>Lvl</b></td><td style="white-space:nowrap"><b>Code</b></td><td><b>Display</b></td><td><b>Definition</b></td><td><b>internalId</b></td><td><b>status</b></td><td><b>synonymCode</b></td></tr><tr><td>1</td><td style="white-space:nowrap">application<a name="v3-mediatypes-application"> </a></td><td>ApplicationMediaType</td><td>Application specific media type.</td><td>21083</td><td>active</td><td/></tr><tr><td>2</td><td style="white-space:nowrap"> application/dicom<a name="v3-mediatypes-application.47dicom"> </a></td><td>DICOM</td><td>Digital Imaging and Communications in Medicine (DICOM) MIME type defined in RFC3240 \[http://ietf.org/rfc/rfc3240.txt\].</td><td>21460</td><td>active</td><td/></tr><tr><td>2</td><td style="white-space:nowrap"> application/msword<a name="v3-mediatypes-application.47msword"> </a></td><td>MSWORD</td><td>This format is very prone to compatibility problems. If sharing of edit-able text is required, text/plain, text/html or text/rtf should be used instead.</td><td>14834</td><td>active</td><td/></tr><tr><td>2</td><td style="white-space:nowrap"> application/pdf<a name="v3-mediatypes-application.47pdf"> </a></td><td>PDF</td><td>The Portable Document Format is recommended for written text that is completely laid out and read-only. PDF is a platform independent, widely deployed, and open specification with freely available creation and rendering tools.</td><td>14833</td><td>active</td><td/></tr><tr><td>1</td><td style="white-space:nowrap">audio<a name="v3-mediatypes-audio"> </a></td><td>AudioMediaType</td><td>Audio media type.</td><td>21084</td><td>active</td><td/></tr><tr><td>2</td><td style="white-space:nowrap"> audio/basic<a name="v3-mediatypes-audio.47basic"> </a></td><td>Basic Audio</td><td>This is a format for single channel audio, encoded using 8bit ISDN mu-law \[PCM\] at a sample rate of 8000 Hz. This format is standardized by: CCITT, Fascicle III.4 -Recommendation G.711. Pulse Code Modulation (PCM) of Voice Frequencies. Geneva, 1972.</td><td>14836</td><td>active</td><td/></tr><tr><td>2</td><td style="white-space:nowrap"> audio/k32adpcm<a name="v3-mediatypes-audio.47k32adpcm"> </a></td><td>K32ADPCM Audio</td><td>ADPCM allows compressing audio data. It is defined in the Internet specification RFC 2421 \[ftp://ftp.isi.edu/in-notes/rfc2421.txt\]. Its implementation base is unclear.</td><td>14838</td><td>active</td><td/></tr><tr><td>2</td><td style="white-space:nowrap"> audio/mpeg<a name="v3-mediatypes-audio.47mpeg"> </a></td><td>MPEG audio layer 3</td><td>MPEG-1 Audio layer-3 is an audio compression algorithm and file format defined in ISO 11172-3 and ISO 13818-3. MP3 has an adjustable sampling frequency for highly compressed telephone to CD quality audio.</td><td>14837</td><td>active</td><td/></tr><tr><td>1</td><td style="white-space:nowrap">image<a name="v3-mediatypes-image"> </a></td><td>ImageMediaType</td><td>Image media type.</td><td>21085</td><td>active</td><td/></tr><tr><td>2</td><td style="white-space:nowrap"> image/g3fax<a name="v3-mediatypes-image.47g3fax"> </a></td><td>G3Fax Image</td><td>This is recommended only for fax applications.</td><td>14843</td><td>active</td><td/></tr><tr><td>2</td><td style="white-space:nowrap"> image/gif<a name="v3-mediatypes-image.47gif"> </a></td><td>GIF Image</td><td>GIF is a popular format that is universally well supported. However GIF is patent encumbered and should therefore be used with caution.</td><td>14841</td><td>active</td><td/></tr><tr><td>2</td><td style="white-space:nowrap"> image/jpeg<a name="v3-mediatypes-image.47jpeg"> </a></td><td>JPEG Image</td><td>This format is required for high compression of high color photographs. It is a "lossy" compression, but the difference to lossless compression is almost unnoticeable to the human vision.</td><td>14842</td><td>active</td><td/></tr><tr><td>2</td><td style="white-space:nowrap"> image/png<a name="v3-mediatypes-image.47png"> </a></td><td>PNG Image</td><td>Portable Network Graphics (PNG) \[http://www.cdrom.com/pub/png\] is a widely supported lossless image compression standard with open source code available.</td><td>14840</td><td>active</td><td/></tr><tr><td>2</td><td style="white-space:nowrap"> image/tiff<a name="v3-mediatypes-image.47tiff"> </a></td><td>TIFF Image</td><td>Although TIFF (Tag Image File Format) is an international standard it has many interoperability problems in practice. Too many different versions that are not handled by all software alike.</td><td>14844</td><td>active</td><td/></tr><tr><td>1</td><td style="white-space:nowrap">model<a name="v3-mediatypes-model"> </a></td><td>ModelMediaType</td><td>Model media type.</td><td>21086</td><td>active</td><td/></tr><tr><td>2</td><td style="white-space:nowrap"> model/vrml<a name="v3-mediatypes-model.47vrml"> </a></td><td>VRML Model</td><td>This is an openly standardized format for 3D models that can be useful for virtual reality applications such as anatomy or biochemical research (visualization of the steric structure of macromolecules)</td><td>14849</td><td>active</td><td/></tr><tr><td>1</td><td style="white-space:nowrap">multipart<a name="v3-mediatypes-multipart"> </a></td><td>MultipartMediaType</td><td>Multipart Media Type</td><td>21087</td><td>active</td><td/></tr><tr><td>2</td><td style="white-space:nowrap"> multipart/x-hl7-cda-level-one<a name="v3-mediatypes-multipart.47x-hl7-cda-level-one"> </a></td><td>CDA Level 1 Multipart</td><td>The HL7 clinical document Architecture, Level 1 MIME package.</td><td>14851</td><td>active</td><td>multipart/x-hl7-cda-level1</td></tr><tr><td>2</td><td style="white-space:nowrap"> multipart/x-hl7-cda-level1<a name="v3-mediatypes-multipart.47x-hl7-cda-level1"> </a></td><td>CDA Level 1 Multipart</td><td>The HL7 clinical document Architecture, Level 1 MIME package.</td><td>14851</td><td>retired</td><td>multipart/x-hl7-cda-level-one</td></tr><tr><td>1</td><td style="white-space:nowrap">text<a name="v3-mediatypes-text"> </a></td><td>TextMediaType</td><td>For any text</td><td>21088</td><td>active</td><td/></tr><tr><td>2</td><td style="white-space:nowrap"> text/html<a name="v3-mediatypes-text.47html"> </a></td><td>HTML Text</td><td>For marked-up text according to the Hypertext Mark-up Language. HTML markup is sufficient for typographically marking-up most written-text documents. HTML is platform independent and widely deployed.</td><td>14828</td><td>active</td><td/></tr><tr><td>2</td><td style="white-space:nowrap"> text/plain<a name="v3-mediatypes-text.47plain"> </a></td><td>Plain Text</td><td>**Description:**For any plain text. This is the default and is used for a character string (ST) data type.</td><td>14826</td><td>active</td><td/></tr><tr><td>2</td><td style="white-space:nowrap"> text/rtf<a name="v3-mediatypes-text.47rtf"> </a></td><td>RTF Text</td><td>The Rich Text Format is widely used to share word-processor documents. However, RTF does have compatibility problems, as it is quite dependent on the word processor. May be useful if word processor edit-able text should be shared.</td><td>14831</td><td>active</td><td/></tr><tr><td>2</td><td style="white-space:nowrap"> text/sgml<a name="v3-mediatypes-text.47sgml"> </a></td><td>SGML Text</td><td>For structured character based data. There is a risk that general SGML/XML is too powerful to allow a sharing of general SGML/XML documents between different applications.</td><td>14829</td><td>active</td><td/></tr><tr><td>2</td><td style="white-space:nowrap"> text/x-hl7-ft<a name="v3-mediatypes-text.47x-hl7-ft"> </a></td><td>HL7 Text</td><td>For compatibility, this represents the HL7 v2.x FT data type. Its use is recommended only for backward compatibility with HL7 v2.x systems.</td><td>14827</td><td>active</td><td/></tr><tr><td>2</td><td style="white-space:nowrap"> text/x-hl7-text+xml<a name="v3-mediatypes-text.47x-hl7-text.43xml"> </a></td><td>HL7 Structured Narrative</td><td>**Description:** The content described by the CDA Narrative Block (not just used by CDA).</td><td>22607</td><td>active</td><td/></tr><tr><td>2</td><td style="white-space:nowrap"> text/xml<a name="v3-mediatypes-text.47xml"> </a></td><td>XML Text</td><td>For structured character based data. There is a risk that general SGML/XML is too powerful to allow a sharing of general SGML/XML documents between different applications.</td><td>14830</td><td>active</td><td/></tr><tr><td>1</td><td style="white-space:nowrap">video<a name="v3-mediatypes-video"> </a></td><td>VideoMediaType</td><td>Video media type.</td><td>21089</td><td>active</td><td/></tr><tr><td>2</td><td style="white-space:nowrap"> video/mpeg<a name="v3-mediatypes-video.47mpeg"> </a></td><td>MPEG Video</td><td>MPEG is an international standard, widely deployed, highly efficient for high color video; open source code exists; highly interoperable.</td><td>14846</td><td>active</td><td/></tr><tr><td>2</td><td style="white-space:nowrap"> video/x-avi<a name="v3-mediatypes-video.47x-avi"> </a></td><td>X-AVI Video</td><td>The AVI file format is just a wrapper for many different codecs; it is a source of many interoperability problems.</td><td>14847</td><td>active</td><td/></tr></table><p><b>Additional Language Displays</b></p><table class="codes"><tr><td><b>Code</b></td><td><b>English (English, en)</b></td></tr><tr><td>application</td><td></td></tr><tr><td>audio</td><td></td></tr><tr><td>image</td><td></td></tr><tr><td>model</td><td></td></tr><tr><td>multipart</td><td></td></tr><tr><td>text</td><td></td></tr><tr><td>video</td><td></td></tr></table></div> </text> <url value="http://terminology.hl7.org/CodeSystem/v3-mediatypes"/> <identifier> <system value="urn:ietf:rfc:3986"/> <value value="urn:oid:2.16.840.1.113883.5.79"/> </identifier> <version value="2.0.0"/> <name value="MediaType"/> <title value="Media Type"/> <status value="active"/> <date value="2019-03-20T00:00:00-04:00"/> <publisher value="Health Level 7"/> <contact> <name value="Health Level Seven"/> </contact> <description value="Internet Assigned Numbers Authority (IANA) Mime Media Types. Identifies the type of the encapsulated data and identifies a method to interpret or render the data. The IANA defined domain of media types is established by the Internet standard RFC 2045 \[http://www.ietf.org/rfc/rfc2045.txt\] and 2046 \[http://www.ietf.org/rfc/rfc2046.txt\]. RFC 2046 defines the media type to consist of two parts: 1. top level media type, and 2. media subtype However, this HL7 datatypes specification treats the entire media type as one atomic code symbol in the form defined by IANA, i.e., top level type followed by a slash "/" followed by media subtype. Currently defined media types are registered in a database \[http://www.iana.org/assignments/media-types/index.html\] maintained by IANA. Currently several hundred different MIME media types are defined, with the list growing rapidly. In general, all those types defined by the IANA syntax MAY be used. This code system is a substet of all possible media type codes which are used in HL7 Standaards and Implementation Guides. More information and documentation of this content can be found at Multipurpose Internet Mail Extensions (MIME) Part Four - BCP 13. \[http://tools.ietf.org/html/bcp13\] "/> <hierarchyMeaning value="is-a"/> <content value="fragment"/> <property> <extension url="http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-symmetry"> <valueCode value="antisymmetric"/> </extension> <extension url="http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-transitivity"> <valueCode value="transitive"/> </extension> <extension url="http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-reflexivity"> <valueCode value="irreflexive"/> </extension> <extension url="http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-isNavigable"> <valueBoolean value="true"/> </extension> <extension url="http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-relationshipKind"> <valueCode value="Specializes"/> </extension> <extension url="http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-inverseName"> <valueString value="Generalizes"/> </extension> <code value="Specializes"/> <description value="The child code is a more narrow version of the concept represented by the parent code. I.e. Every child concept is also a valid parent concept. Used to allow determination of subsumption. Must be transitive, irreflexive, antisymmetric."/> <type value="Coding"/> </property> <property> <extension url="http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-symmetry"> <valueCode value="antisymmetric"/> </extension> <extension url="http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-transitivity"> <valueCode value="transitive"/> </extension> <extension url="http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-reflexivity"> <valueCode value="irreflexive"/> </extension> <extension url="http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-isNavigable"> <valueBoolean value="true"/> </extension> <extension url="http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-relationshipKind"> <valueCode value="Generalizes"/> </extension> <extension url="http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-inverseName"> <valueString value="Specializes"/> </extension> <code value="Generalizes"/> <description value="Inverse of Specializes. Only included as a derived relationship."/> <type value="Coding"/> </property> <property> <code value="internalId"/> <uri value="http://terminology.hl7.org/CodeSystem/utg-concept-properties#v3-internal-id"/> <description value="The internal identifier for the concept in the HL7 Access database repository."/> <type value="code"/> </property> <property> <code value="status"/> <uri value="http://hl7.org/fhir/concept-properties#status"/> <description value="Designation of a concept's state. Normally is not populated unless the state is retired."/> <type value="code"/> </property> <property> <code value="synonymCode"/> <uri value="http://hl7.org/fhir/concept-properties#synonym"/> <description value="An additional concept code that was also attributed to a concept"/> <type value="code"/> </property> <concept> <code value="application"/> <display value="ApplicationMediaType"/> <definition value="Application specific media type."/> <property> <code value="status"/> <valueCode value="active"/> </property> <property> <code value="internalId"/> <valueCode value="21083"/> </property> <concept> <code value="application/dicom"/> <display value="DICOM"/> <definition value="Digital Imaging and Communications in Medicine (DICOM) MIME type defined in RFC3240 \[http://ietf.org/rfc/rfc3240.txt\]."/> <property> <code value="status"/> <valueCode value="active"/> </property> <property> <code value="internalId"/> <valueCode value="21460"/> </property> </concept> <concept> <code value="application/msword"/> <display value="MSWORD"/> <definition value="This format is very prone to compatibility problems. If sharing of edit-able text is required, text/plain, text/html or text/rtf should be used instead."/> <property> <code value="status"/> <valueCode value="active"/> </property> <property> <code value="internalId"/> <valueCode value="14834"/> </property> </concept> <concept> <code value="application/pdf"/> <display value="PDF"/> <definition value="The Portable Document Format is recommended for written text that is completely laid out and read-only. PDF is a platform independent, widely deployed, and open specification with freely available creation and rendering tools."/> <property> <code value="status"/> <valueCode value="active"/> </property> <property> <code value="internalId"/> <valueCode value="14833"/> </property> </concept> </concept> <concept> <code value="audio"/> <display value="AudioMediaType"/> <definition value="Audio media type."/> <property> <code value="status"/> <valueCode value="active"/> </property> <property> <code value="internalId"/> <valueCode value="21084"/> </property> <concept> <code value="audio/basic"/> <display value="Basic Audio"/> <definition value="This is a format for single channel audio, encoded using 8bit ISDN mu-law \[PCM\] at a sample rate of 8000 Hz. This format is standardized by: CCITT, Fascicle III.4 -Recommendation G.711. Pulse Code Modulation (PCM) of Voice Frequencies. Geneva, 1972."/> <property> <code value="status"/> <valueCode value="active"/> </property> <property> <code value="internalId"/> <valueCode value="14836"/> </property> </concept> <concept> <code value="audio/k32adpcm"/> <display value="K32ADPCM Audio"/> <definition value="ADPCM allows compressing audio data. It is defined in the Internet specification RFC 2421 \[ftp://ftp.isi.edu/in-notes/rfc2421.txt\]. Its implementation base is unclear."/> <property> <code value="status"/> <valueCode value="active"/> </property> <property> <code value="internalId"/> <valueCode value="14838"/> </property> </concept> <concept> <code value="audio/mpeg"/> <display value="MPEG audio layer 3"/> <definition value="MPEG-1 Audio layer-3 is an audio compression algorithm and file format defined in ISO 11172-3 and ISO 13818-3. MP3 has an adjustable sampling frequency for highly compressed telephone to CD quality audio."/> <designation> <language value="en"/> <use> <system value="http://snomed.info/sct"/> <code value="900000000000013009"/> </use> <value value="MP3 Audio"/> </designation> <property> <code value="status"/> <valueCode value="active"/> </property> <property> <code value="internalId"/> <valueCode value="14837"/> </property> </concept> </concept> <concept> <code value="image"/> <display value="ImageMediaType"/> <definition value="Image media type."/> <property> <code value="status"/> <valueCode value="active"/> </property> <property> <code value="internalId"/> <valueCode value="21085"/> </property> <concept> <code value="image/g3fax"/> <display value="G3Fax Image"/> <definition value="This is recommended only for fax applications."/> <property> <code value="status"/> <valueCode value="active"/> </property> <property> <code value="internalId"/> <valueCode value="14843"/> </property> </concept> <concept> <code value="image/gif"/> <display value="GIF Image"/> <definition value="GIF is a popular format that is universally well supported. However GIF is patent encumbered and should therefore be used with caution."/> <property> <code value="status"/> <valueCode value="active"/> </property> <property> <code value="internalId"/> <valueCode value="14841"/> </property> </concept> <concept> <code value="image/jpeg"/> <display value="JPEG Image"/> <definition value="This format is required for high compression of high color photographs. It is a "lossy" compression, but the difference to lossless compression is almost unnoticeable to the human vision."/> <property> <code value="status"/> <valueCode value="active"/> </property> <property> <code value="internalId"/> <valueCode value="14842"/> </property> </concept> <concept> <code value="image/png"/> <display value="PNG Image"/> <definition value="Portable Network Graphics (PNG) \[http://www.cdrom.com/pub/png\] is a widely supported lossless image compression standard with open source code available."/> <property> <code value="status"/> <valueCode value="active"/> </property> <property> <code value="internalId"/> <valueCode value="14840"/> </property> </concept> <concept> <code value="image/tiff"/> <display value="TIFF Image"/> <definition value="Although TIFF (Tag Image File Format) is an international standard it has many interoperability problems in practice. Too many different versions that are not handled by all software alike."/> <property> <code value="status"/> <valueCode value="active"/> </property> <property> <code value="internalId"/> <valueCode value="14844"/> </property> </concept> </concept> <concept> <code value="model"/> <display value="ModelMediaType"/> <definition value="Model media type."/> <property> <code value="status"/> <valueCode value="active"/> </property> <property> <code value="internalId"/> <valueCode value="21086"/> </property> <concept> <code value="model/vrml"/> <display value="VRML Model"/> <definition value="This is an openly standardized format for 3D models that can be useful for virtual reality applications such as anatomy or biochemical research (visualization of the steric structure of macromolecules)"/> <property> <code value="status"/> <valueCode value="active"/> </property> <property> <code value="internalId"/> <valueCode value="14849"/> </property> </concept> </concept> <concept> <code value="multipart"/> <display value="MultipartMediaType"/> <definition value="Multipart Media Type"/> <property> <code value="status"/> <valueCode value="active"/> </property> <property> <code value="internalId"/> <valueCode value="21087"/> </property> <concept> <code value="multipart/x-hl7-cda-level-one"/> <display value="CDA Level 1 Multipart"/> <definition value="The HL7 clinical document Architecture, Level 1 MIME package."/> <property> <code value="status"/> <valueCode value="active"/> </property> <property> <code value="synonymCode"/> <valueCode value="multipart/x-hl7-cda-level1"/> </property> <property> <code value="internalId"/> <valueCode value="14851"/> </property> </concept> <concept> <code value="multipart/x-hl7-cda-level1"/> <display value="CDA Level 1 Multipart"/> <definition value="The HL7 clinical document Architecture, Level 1 MIME package."/> <property> <code value="status"/> <valueCode value="retired"/> </property> <property> <code value="synonymCode"/> <valueCode value="multipart/x-hl7-cda-level-one"/> </property> <property> <code value="internalId"/> <valueCode value="14851"/> </property> </concept> </concept> <concept> <code value="text"/> <display value="TextMediaType"/> <definition value="For any text"/> <property> <code value="status"/> <valueCode value="active"/> </property> <property> <code value="internalId"/> <valueCode value="21088"/> </property> <concept> <code value="text/html"/> <display value="HTML Text"/> <definition value="For marked-up text according to the Hypertext Mark-up Language. HTML markup is sufficient for typographically marking-up most written-text documents. HTML is platform independent and widely deployed."/> <property> <code value="status"/> <valueCode value="active"/> </property> <property> <code value="internalId"/> <valueCode value="14828"/> </property> </concept> <concept> <code value="text/plain"/> <display value="Plain Text"/> <definition value="**Description:**For any plain text. This is the default and is used for a character string (ST) data type."/> <property> <code value="status"/> <valueCode value="active"/> </property> <property> <code value="internalId"/> <valueCode value="14826"/> </property> </concept> <concept> <code value="text/rtf"/> <display value="RTF Text"/> <definition value="The Rich Text Format is widely used to share word-processor documents. However, RTF does have compatibility problems, as it is quite dependent on the word processor. May be useful if word processor edit-able text should be shared."/> <property> <code value="status"/> <valueCode value="active"/> </property> <property> <code value="internalId"/> <valueCode value="14831"/> </property> </concept> <concept> <code value="text/sgml"/> <display value="SGML Text"/> <definition value="For structured character based data. There is a risk that general SGML/XML is too powerful to allow a sharing of general SGML/XML documents between different applications."/> <property> <code value="status"/> <valueCode value="active"/> </property> <property> <code value="internalId"/> <valueCode value="14829"/> </property> </concept> <concept> <code value="text/x-hl7-ft"/> <display value="HL7 Text"/> <definition value="For compatibility, this represents the HL7 v2.x FT data type. Its use is recommended only for backward compatibility with HL7 v2.x systems."/> <property> <code value="status"/> <valueCode value="active"/> </property> <property> <code value="internalId"/> <valueCode value="14827"/> </property> </concept> <concept> <code value="text/x-hl7-text+xml"/> <display value="HL7 Structured Narrative"/> <definition value="**Description:** The content described by the CDA Narrative Block (not just used by CDA)."/> <property> <code value="status"/> <valueCode value="active"/> </property> <property> <code value="internalId"/> <valueCode value="22607"/> </property> </concept> <concept> <code value="text/xml"/> <display value="XML Text"/> <definition value="For structured character based data. There is a risk that general SGML/XML is too powerful to allow a sharing of general SGML/XML documents between different applications."/> <property> <code value="status"/> <valueCode value="active"/> </property> <property> <code value="internalId"/> <valueCode value="14830"/> </property> </concept> </concept> <concept> <code value="video"/> <display value="VideoMediaType"/> <definition value="Video media type."/> <property> <code value="status"/> <valueCode value="active"/> </property> <property> <code value="internalId"/> <valueCode value="21089"/> </property> <concept> <code value="video/mpeg"/> <display value="MPEG Video"/> <definition value="MPEG is an international standard, widely deployed, highly efficient for high color video; open source code exists; highly interoperable."/> <property> <code value="status"/> <valueCode value="active"/> </property> <property> <code value="internalId"/> <valueCode value="14846"/> </property> </concept> <concept> <code value="video/x-avi"/> <display value="X-AVI Video"/> <definition value="The AVI file format is just a wrapper for many different codecs; it is a source of many interoperability problems."/> <property> <code value="status"/> <valueCode value="active"/> </property> <property> <code value="internalId"/> <valueCode value="14847"/> </property> </concept> </concept> </CodeSystem>
IG © 2020+ HL7 International - Vocabulary Work Group. Package hl7.terminology#1.0.0 based on FHIR 4.0.1. Generated 2020-05-09
Links: Table of Contents |
QA Report | Search
| Version History |
Propose a change