Hi All,
Yeah, this was actually the use cases/requirements document that we used initially for RHEA.
Basically when we first looked at Apelon DTS, we were evaluating it against this document.
(our requirements document available at https://jembiprojects.jira.com/wiki/display/RHEAPILOT/Terminology+Service is directly derived from it)
Most of the cases described here focus on a system-as-a-whole level:
e.g. “The system must provide a method to load a mass number (i.e. a bulk loading) of the coding system elements”
reads as “a user should be able to do this using a tool like DTS Editor”.
Specifically the doc covers two “interoperability”-level use cases: code verification and mapping.
So this just got me thinking that it might good the differentiate between our “users” for the TS,
and this then we can classify and think about the use cases in different ways.
In Rwanda we think about three types of users (thinking that derived from the document you sent out Jonathan ):
-
Maintainers who interface with the TS in order to maintain terminologies
-
Health professionals who want to look up and browse terminologies using, say, a web browser
-
The Interoperability Layer: This the back-end “service” level. This was basically what I had in my head when thinking
about the use cases for this particular exercise (and which is why I didn’t think to sent out the Rwanda requirements verbatim ).
So this is where the interoperability interfaces and standards will come into play.
Kind Regards
Hannes
···
On Thu, Jun 27, 2013 at 4:48 PM, Jonathan Payne paynejd@gmail.com wrote:
Yes, it’s specific to Rwanda needs, but many of the use cases are pretty generic. It will be interesting to note requirements that are unique to Rwanda as well though.
On Jun 27, 2013, at 10:47 AM, Andrew Kanter ask7002@dbmi.columbia.edu wrote:
Thanks, Jonathan! Was this for Rwanda, though?
Andrew S. Kanter, MD MPH FACMI
Asst. Prof. Clinical Biomedical Informatics
and Clinical Epidemiology
622 W. 168th Street, VC5 (VC-562)
New York, NY 10032
Email: andrew.kanter@dbmi.columbia.edu
Office: +1 212 305 4842
Cell: +1 646 469 2421
Skype: akanter-ippnw
On Jun 27, 2013, at 9:49 AM, Jonathan Payne paynejd@gmail.com wrote:
See the attached Terminology Services Requirements document that the rock star Liz Peloso put together for Nigeria. This has a good 2 pages of functional requirements and use cases.
–
You received this message because you are subscribed to the Google Groups “Terminology Services” group.
To unsubscribe from this group and stop receiving emails from it, send an email to terminology-services+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
–
You received this message because you are subscribed to the Google Groups “Terminology Services” group.
To unsubscribe from this group and stop receiving emails from it, send an email to terminology-services+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
–
Hannes Venter
Software Developer, Jembi Health Systems | SOUTH AFRICA
Mobile: +27 73 276 2848 | Office: +27 21 701 0939 | Skype: venter.johannes
E-mail: hannes@jembi.org
–
Jonathan Payne, MS
615.579.5413
skype: jonathandavidpayne
On Thu, Jun 27, 2013 at 9:34 AM, Hannes Venter hannes@jembi.org wrote:
- Code validation: verify that a terminology code is valid member of a specified terminology code space
– Bulk validation: validate a set of codes against a specified code space
- Check for updates: request a list of codes for a particular code space that have been added/changed since a specified date
- Export: return the codes within a specified code space (or sub-space thereof) in a standard format (e.g. xml, csv, etc.)
- Support localization: For a specified code, return the concept term in a specific language
Regards
–
Hannes Venter
Software Developer, Jembi Health Systems | SOUTH AFRICA
Mobile: +27 73 276 2848 | Office: +27 21 701 0939 | Skype: venter.johannes
E-mail: hannes@jembi.org
Hannes
–
You received this message because you are subscribed to the Google Groups “Terminology Services” group.
To unsubscribe from this group and stop receiving emails from it, send an email to terminology-services+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.