Replies: 6 comments
-
Hey @scavet64, thank you for the comments. Glad that my library is helping! In regards to the
I'll add an Issue to fix for V2.51. Do you have any references that would help clear up for V2.6? I sometimes refer to Caristix, though I can't really comment on how reliable their HL7 definition is. https://hl7-definition.caristix.com/v2/HL7v2.6/Segments/OBX |
Beta Was this translation helpful? Give feedback.
-
I've created a new issue for V2.51 item: #9 |
Beta Was this translation helpful? Give feedback.
-
I referred to the Medical Records/Information Management specification for 2.6, and it also calls for a variable datatype. Not ChannelDefinition, as the Appendix document claims. This matches with every other OBX reference from V2.6 that I checked against on the web. So I'm going to update clear-hl7-net to use |
Beta Was this translation helpful? Give feedback.
-
I've created a new issue for V2.60 item: #10 |
Beta Was this translation helpful? Give feedback.
-
Changes now implemented in the v2-enhancements branch. |
Beta Was this translation helpful? Give feedback.
-
v2-beta1 has now been published to NuGet with the |
Beta Was this translation helpful? Give feedback.
-
I was curious why the
ObservationValue
in the classObxSegment
for v2.5.1 and v2.6.0 are of typeChannelDefinition
while the rest of the classes have that property as typeIEnumerable<string>
?To my understanding, that field's type can vary depending on the value in OBX.2 according to the spec. With that in mind I was thinking that changing
ObservationValue
's data type to IType would resolve that issue. Would that change be inline with your thinking as well?I have only recently started working with the HL7 format and thanks to your library I've been able to piece it together and get a better grasp so thanks again!
Beta Was this translation helpful? Give feedback.
All reactions