Loading...
Help
Login
Busy
Search
HL7 V2.5 International (xml) - Project Information
 
Warning
Select building block repository
Select user
Select user

Add/change logo
Remove File
Compare: Releases


Edit
Edit publication parameters

Warning
Edit
Edit
Name
HL7 V2.5 International (xml)
Description

HL7 V2.5 International for use with XML serialization.

NOTE: This specification is a conversion to DECOR that includes Template ITS done by the ART-DECOR expert group for implementation purposes and has no official endorsement or involvement from HL7 International.

Usage Notes

  • This conversion has been compiled with utmost care, but the source of truth for HL7 V2 is the official version as published by HL7 International.
  • This conversion consists of messages, segments and datatypes. The specificatie does not contain distinct field definition templates, as those are contained in the segment templates. Reuse of fields in Z-segments may be a little more difficult but in turn it makes the specification much more readable
  • Included in this conversion:
    • Messages carrying the name from the event (message namesn are not available)
    • Segments carrying the segment name. All segment fields including name, item-ID, datatype, HL7 Table, conformance, cardinality
    • Datatypes carrying the datatype name. All datatype sub fields including name, description, datatype, HL7 Table, conformance, cardinality
  • Excluded from this conversion:
    • Maximum length of fields. Thid informatie was inconsistent in the base HL7 V2.5 and is considered a guideline to make site agreements for. To included it in this specification would only provide more work for specifiers/implementers.
    • Message, segment and field definitions/descriptions. This information is not contained in the v2.xml schemas and would need to be copied in by hand from the guidse chapters. This work was only done for the datatypes by copying chapter 2A
PropertiesPrefix: ad4bbr-Default language: English (en-US)Contains reusable content?The contents of this 'project' are considered suitable for re-use by other projects when this setting is active.Is private?The project is not listed in the menus and ignored in searches when this setting is active. This useful for projects in incubation fase. You may still work in the project based on direct URLsExperimental/Test?Project is experimental or meant to test things rather than aimed at production useNotifier: Determines the project global issue notifier setting (on/off - default is 'on'). Note: changes to this setting are immediately saved.
Publication location
http://ad4bbr.art-decor.org/
Project overviewProject Index
Project Id2.16.840.1.113883.3.1937.777.10
Project Last modified2019-03-30 05:35:45
Repository reference
RESTful Service
Contributors/Copyright
ContributorTypeLogoCopyright years
HL7 International
Health Level Seven International
3300 Washtenaw Avenue
Suite 227
Ann Arbor, MI 48104- 4261
USA
+1 734 677 7777
+1 734 677 6622 (Fax)
info@hl7.org
Author2012-2015
The ART-DECOR expert group
info@art-decor.org
contact@art-decor.org
Author2012-2015
Authors
NameEmailSubscribe to all issuesEvery author is notified by default for events on issues where he is the author or from the moment he is assigned to an issue. If you would like to keep track of all issue updates, set this to 'on'
Alexander HenketNot visibleThis info is only visible to this author and any decor-admin authorNot visibleThis info is only visible to this author and any decor-admin author
Kai HeitmannNot visibleThis info is only visible to this author and any decor-admin authorNot visibleThis info is only visible to this author and any decor-admin author
Versions / Releases
Warning



ReadyBusyError
DateByDescriptionStatusPublication
2016-10-16Alexander Henket
  • Added full datatype description texts
  • Added Dutch translation for the datatype main texts, i.e. not for individual (sub)subcomponents
2016-10-12Alexander Henket
  • Added missing display names on templates where available (messages/segments/datatypes)
  • Added missing structure info on message level templates as relationship/@model
2015-07-18Alexander Henket

This original demo4- project was assigned a proper OID for production use and extended with all HL7 V2.5 tables based on the FHIR V2 Tables XML source.xml. Caveats:

  • Empty tables were skipped.
  • There are several tables that have an expression for the code value instead of a real code. Examples include Table HL70093 and Table HL70485. These value sets are not suited for use as-is but serve example purpose. They are expected to be specialized by those who need them, e.g. in a conformance profile.
  • Every applicable field in the HL7 V2.5 schemas calls the Table as HL7nnnn, hence to keep the connection visibly clear no distinction is made between User Defined Tables and HL7 Tables when naming the DECOR value sets.
  • DECOR value sets require codeSystem OIDs for any code. V2 Tables do not have OIDs for codes. V2 Tables actually are both value set and codesystem. The codesystem in the V2 Tables is therefor assigned in the conversion based on the base-id for codesystems in this repository + table-id as a workaround. The codesystem in the DECOR value sets shall not surface in any message and only serves to satisfy the DECOR value set requirements.
2014-05-09 12:52:00Alexander Henket
Initial release of the first complete ad4bbr (named hl725int-bbr) as conversion from the V2.xml schemas
Busy

MyCommunity
Display NameNameDescription
BusyRetrieving…
Governance Groups
BusyRetrieving…
ART-DECOR Applications (ADA)
Application