Difference between revisions of "PCD SDO HL7 Coordination"
Jump to navigation
Jump to search
ToddCooper (talk | contribs) m (Initial Version) |
ToddCooper (talk | contribs) m (Updated with Phoenix issues) |
||
| Line 11: | Line 11: | ||
''Use the following table to log new issues that need to be addressed.'' | ''Use the following table to log new issues that need to be addressed.'' | ||
| − | :{|border="2" | + | |
| + | :{|border="2" cellpadding="2" | ||
|- | |- | ||
! width="35pt" align="center" |Item | ! width="35pt" align="center" |Item | ||
| Line 18: | Line 19: | ||
! width="200pt" align="left" |Topic | ! width="200pt" align="left" |Topic | ||
! width="400pt" align="left" |Description | ! width="400pt" align="left" |Description | ||
| − | ! width="400pt" align="left" |Disposition | + | ! width="400pt" align="left" |Status/Disposition |
|- | |- | ||
| align="center" | 1 | | align="center" | 1 | ||
| Line 35: | Line 36: | ||
''[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?!'' | ''[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?!'' | ||
| − | :{|border="2" | + | |
| + | :{|border="2" cellpadding="2" | ||
|- | |- | ||
| − | ! width=" | + | ! width="10" align="center" |Item |
| − | ! width=" | + | ! width="15" align="left" |Submitters |
| − | ! width=" | + | ! width="10" align="left" |Profiles |
| − | ! width=" | + | ! width="15" align="left" |Topic |
| − | ! width=" | + | ! width="25" align="left" |Description |
| − | ! width=" | + | ! width="400" align="left" |Status/Disposition |
|- | |- | ||
| align="center" | 1 | | align="center" | 1 | ||
| + | | TCooper | ||
| + | | DEC, PIV, SPD | ||
| + | | v2.x Message Registration | ||
| + | | There was discussion during development of the [DEC] profile that the resulting message should be "registered" in order to support conformance validation. This question has come up again for the PIV and SPD development, espeically with respect to the value for MSH-21 Message Profile Identifier. See HL7 v2.6 chapter 2.14.9.21. | ||
| + | | . | ||
| + | |- | ||
| + | | align="center" | 2 | ||
| + | | PSchluter | ||
| + | | ACM | ||
| + | | v2.x OBX's w/ simiple wave data | ||
| + | | The ACM profile needs a simple method for communicating wave snippet data that is associated with an alarm condition. The desire is to have wave sample information communicated vs. an image representation of the wave. Since the output devices upon which the wave data will be displayed can vary widely w.r.t. their capabilities, the data format should be very simple, such that it can be easily transformed to a presentation format appropriate to the display / reviewer device. | ||
| + | | Notes: | ||
| + | :* This should also apply to the DEC profile | ||
| + | :* Extensibility to annotation data should also be supported | ||
| + | :* Could a URL be passed linking to the wave data? | ||
| + | |- | ||
| + | | align="center" | 3 | ||
| + | | MPatillo | ||
| + | | ACM | ||
| + | | v2.x assignment of a non-"Z" trigger event | ||
| + | | '''''<Monroe - add a description here>''''' | ||
| + | | . | ||
| + | |- | ||
| + | | align="center" | 4 | ||
| + | | JRhinda | ||
| + | | PIV | ||
| + | | Response reporting of actual settings | ||
| + | | '''''<Jeff - add a description here>''''' | ||
| + | | . | ||
| + | |- | ||
| + | | align="center" | 5 | ||
| + | | tbd | ||
| + | | . | ||
| + | | . | ||
| + | | . | ||
| + | | . | ||
| + | |- | ||
| + | | align="center" | 6 | ||
| + | | tbd | ||
| + | | . | ||
| + | | . | ||
| + | | . | ||
| + | | . | ||
| + | |- | ||
| + | | align="center" | 7 | ||
| + | | tbd | ||
| + | | . | ||
| . | | . | ||
| + | | . | ||
| + | | . | ||
| + | |- | ||
| + | | align="center" | 8 | ||
| + | | tbd | ||
| + | | . | ||
| + | | . | ||
| + | | . | ||
| + | | . | ||
| + | |- | ||
| + | | align="center" | 9 | ||
| + | | tbd | ||
| + | | . | ||
| + | | . | ||
| + | | . | ||
| + | | . | ||
| + | |- | ||
| + | | align="center" | 10 | ||
| + | | tbd | ||
| . | | . | ||
| . | | . | ||
Revision as of 21:17, 1 May 2008
HL7 Technical Coordination
The IHE PCD Technical Framework and profile supplements leverage HL7 standards, but during the development phase, questions often arise regarding which HL7 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.
Additionally, IHE is forming an HL7 technical support group that may be able to address many of these issues in the future.
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 DEC, PIV, SPD v2.x Message Registration There was discussion during development of the [DEC] profile that the resulting message should be "registered" in order to support conformance validation. This question has come up again for the PIV and SPD development, espeically with respect to the value for MSH-21 Message Profile Identifier. See HL7 v2.6 chapter 2.14.9.21. . 2 PSchluter ACM v2.x OBX's w/ simiple wave data The ACM profile needs a simple method for communicating wave snippet data that is associated with an alarm condition. The desire is to have wave sample information communicated vs. an image representation of the wave. Since the output devices upon which the wave data will be displayed can vary widely w.r.t. their capabilities, the data format should be very simple, such that it can be easily transformed to a presentation format appropriate to the display / reviewer device. Notes: - This should also apply to the DEC profile
- Extensibility to annotation data should also be supported
- Could a URL be passed linking to the wave data?
3 MPatillo ACM v2.x assignment of a non-"Z" trigger event <Monroe - add a description here> . 4 JRhinda PIV Response reporting of actual settings <Jeff - add a description here> . 5 tbd . . . . 6 tbd . . . . 7 tbd . . . . 8 tbd . . . . 9 tbd . . . . 10 tbd . . . .