PCD SDO IEEE Coordination

From IHE Wiki
Revision as of 13:06, 2 May 2008 by ToddCooper (talk | contribs) (Updated column widths.)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

IEEE Technical Coordination

The IHE PCD Technical Framework and profile supplements leverage IEEE standards, but during the development phase, questions often arise regarding which IEEE standards and components should be used, how they should be used, or resolution of gaps that are surfaced. This page provides PCD membership with a place to log and discuss issues.

Note: In the future, this type of activity may be managed by another tool such as Flyspray. An IHE application of this tool is also available for tracking domain coordination issues.


New Issues

Use the following table to log new issues that need to be addressed.


Item Submitters Profiles Topic Description Status/Disposition
1 . . . . .


Issues for Discussion @ 2008.05.05 HL7/IEEE/ISO Meetings in Phoenix

Use the following table to capture issues to be discussed at the upcoming HL7 meetings in Phoenix.

[TCooper] Should a Date column be added to this table ... for submission or updating ... or is that when we need to use a different tool?!


Item Submitters Profiles Topic Description Status/Disposition
1 TCooper CDA IEEE EUI-64 OID Representation Per IEEE 11073 standards and the [DEC] profile, medical devices are uniquely identified using an EUI-64. HL7 CDA documents rely on ISO Object Identifiers ("OIDs") to encode much of the contained information. After some research, it was determined that there is no existing OID for either naming an EUI-64 data item or for encoding an actual EUI-64. Additionally...
  • In evaluating the correct arc to use for an EUI-64, a comparison was made of the related documentation in ISO/IEEE 11073-00000 Framework & Overview and in ISO/IEEE 11073-10101 Nomenclature. There is a discrepancy between the two arcs. As a result either this problem needs to be resolved or a simplified approach may be used.
  • A general method should be defined for 11073 terminology mapping to ISO OIDs. The mapping need only support the 32-bit context free term codes.

Proposal for IEEE EUI-64 encoding as an ISO OID.

2 tbd . . . .
3 tbd . . . .
4 tbd . . . .
5 tbd . . . .