"Right now, I would go where
there are more tools & technology that correspond to your particular needs."
Thanks. I'd like to release an XML schema that constrains a medical insurance claim (maybe between 10-15 elements). But later, we'll start adding elements/details until the claimants (clinics and hospitals) realize that they have already built an EMR.
I think the claims paradigm is a strong driver for clinic/hospital automation, and releasing a schema for them to comply with (initially just for claims) essentially assures inter-operability at the get go, but it also gives them space to adopt more complex elements when they're ready. If a schema is guiding them throughout, they'll be producing interoperable documents.
"Right now, I would go where
there are more tools & technology that correspond to your particular needs."
Good choice.
Thanks. I'd like to release an XML schema that constrains a medical insurance claim (maybe between 10-15 elements). But later, we'll start adding elements/details until the claimants (clinics and hospitals) realize that they have already built an EMR.
I think the claims paradigm is a strong driver for clinic/hospital automation, and releasing a schema for them to comply with (initially just for claims) essentially assures inter-operability at the get go, but it also gives them space to adopt more complex elements when they're ready. If a schema is guiding them throughout, they'll be producing interoperable documents.