When I teach HL7 classes, I present the following (true) case of an
ill-defined interface.
Client asks me if a physician's drawing could be scanned and then
encoded and embedded into an HL7 message.
I respond - sure, I can encoded it in base64 format and include it in
a Z-segment. However,
-members] Is there an interface with ...?
I see a lot of questions beginning with these few words, and I'm never
quite sure how to respond. In another context, I'd respond with a
question beginning What do you want it to do? Functional requirements
or specifications are rarely discussed here, but before
Something I stumbled across this afternoon that fits here, I think.
http://www.healthcareguy.com/index.php/archives/240#comment-215
Matthew King wrote:
As someone who often asks questions of these types, here is what I
usually mean to ask for a Practice Management Interface:
I see a lot of questions beginning with these few words, and I'm never
quite sure how to respond. In another context, I'd respond with a
question beginning What do you want it to do? Functional requirements
or specifications are rarely discussed here, but before we can
reasonably address the
Hmmm
Speaking with representative of lab equipment etc, I thought that the
answer to Can product ABC interface to software XYZ? was alway
YES. It's always just a 'small' programming fee away... :-)
It's kind of like asking, can we build a bridge from point A to B.
Sure, its always just a
