- Validate whether a CDISC unit is a correct unit for a given (VS) test code
- Validate whether a Vital signs "position" (VSPOS) is a correct "position" for a given (VS) test code
- Validate whether a Character Result/Finding in Standard Format text value (EGSTRESC) for a given ECG Test code (EGTESTCD) is a valid value
All I did is generate a relational database from these lists, and then writing the new web services using RESTful technology.
For example, when you submit:
http://www.xml4pharmaserver.com:8080/CDISCCTService/rest/isValidCDISCUnitForCDISCTestCode/DIABP/mmHg
meaning "validate whether 'mmHg' is a valid CDISC unit for the vital signs test 'DIABP') to the web service, the string "true" is returned, but when you however submit http://www.xml4pharmaserver.com:8080/CDISCCTService/rest/isValidCDISCUnitForCDISCTestCode/HR/mmHg,
the string "false" will be returned.
This is not "rocket science" at all - it took me one evening to create and add the tables to an existing relational database, and about 3 hours to develop, test, and roll out the web services (and write this blog ...).
This is just a first simple example of what is possible, one can easily do similar things for more or even extremely complicated domains such as the LB domain (laboratory) - however in my opinion, we should have a complete rewrite of the LB domain, and use LOINC for the tests, and UCUM for the units.
The complete list (for the new ones, look near the bottom) of the available web services can be found at:
http://www.xml4pharmaserver.com/WebServices/index.html
Are these the kind of web services you would like to see implemented with SHARE? Please let me (and CDISC) know ...