Microsoft Clinical Trial Management Solution

...and another thing.

...about all this crap with HL7 ramming itself into CDISC. This forced merger has created another layer of complexity that is already almost too much to bear. Pity the poor study managers who just want to pass audits and now must mouth not only CDISC but then HL7 XSLT XML transformation gobbledegook??? And for the developers??? Forget about it. Never ending story. Talk about mission creep. It's all too much operationally. People need to post up with Jozef Aerts of xml4pharma and get the lowdown. Not good. C'mon people, sound out if you're in this space or forever hold your peace. This is a marriage from Hell.

Here's one for ya: How can something that is constantly changing be called a "Standard?"

Sign me – eternally confused

sharepointctms.com

OK. Let's Call a Spade a Spade.

I'm done mincing words. Off the shelf portal technologies will be the standard for a Buy-then-Build strategy in development of enterprise clinical trial management systems. Same goes for form development tools. Industry has chosen SharePoint as the portal standard. I like InfoPath for EDC.

Not a siloed solution my ass. They're the very definition of a silo in a world with Enterprise portal technologies. I give MediData and Phasewhatchamacallit about one year before they start touting how they integrate with SharePoint.

Putting money where my mouth is, I just bought sharepointctms.com and infopathedc.com

Tell me I'm wrong.

love,

dave

The Future of EDC Development Tools

The market will evolve to embrace tools based on generic forms development applications with features configured specifically for Clinical Trials. Industry leaders are currently Adobe (Liquid Forms stuff) and MS (InfoPath). Proprietary forms development tools exist today only because they add-in features for clinical trial adaptation that are otherwise unavailable in current versions of Adobe and MS forms development tools. If I were an EDC vendor why would I want to support development of baseline form creation capabilities such as adding in validations, rules, views, roles, privileges, signatures, etc. on top of having to code for integration with web services, databases, xml, n-tier technology etc.. It's almost like trying to create your own word editing program so you can write a protocol. If I were a customer of an EDC vendor I would start looking at the underlying technology and who supports its future development. If it's not Adobe or MS, it's not going to be here long.

 

Sign me- you heard it here first

SharePoint Clinical Trials Portal and Pigs Wearing Lipstick

SharePoint Clinical Trials Portal and Pigs Wearing Lipstick

People are using the word "Portal" a bit loosely these days, to describe web enabled EDC (electronic Data Capture) and CTMS (Clinical Trial Management Systems). Defined as a "a window or gateway to something" I suppose it works, but in the technology sphere, the use of the word "Portal" implies functionality far beyond a round window on a submarine. As an example of this new definition SharePoint represents all that is good about portal technology. It's the modern day reference and will be the Gold Standard by which all others are compared. [ I think its forerunner, at least a similar technology that received wide recognition amongst its field, was DotNetNuke].

The stack provides features that we're coming to expect when using the word Portal to describe certain web based systems. A portal must provide the ability to template sites and functionality. It needs to provide for interconnectivity between sites built on the portal. It should also provide a non-programmatic method for creating these sites and flexibility provisioning these sites with functionality. What is considered "Standard" functionality for portal software is evolving to include document management, workflow, search, lists and granular administration rights and management. Perhaps most importantly it has to allow the user the capability to add their own modules, code and extensions so the platform can integrate with other line of business apps the company is dependent on i.e. it needs to serve as a development platform so stakeholders can respond rapidly to changing business needs.

So next time someone tries to dump their overpriced kludged clinical trial management system or EDC tool on you as a "Portal", ask yourself if what they're offering is really a modern day Portal technology or just another siloed pig in a polk wearing lip stick. If my company were busy installing SharePoint for the enterprise management of business affairs, I'd fire anybody on the spot that didn't recommend one of the available SharePoint solutions for clinical trial management and electronic data capture. It’s a no brainer.

sign me,

You're Fired!

Visio 2010 Workflows Revealed?

Visio 2010 Workflows Revealed?

Not. They might be useful but there isn't a clue to how the images hook up to the objects… if anybody knows, please provide. SPD Workflows even more mysterious.

Breaking News: some info here but still slim guessing:

"..Once you're done with your workflow you can validate it, so that you have not missed any branches or any mandatory information. Then you save it as a Visio or file or better export it as a Visio Workflow Interchange (.vwi file).
In Visio you can only make the actual design of the workflow, not the configuration which is done in SharePoint Designer 2010.
The .vwi file is a zip compressed file containing the XOML files (XAML files for workflows) and some Visio information. This XOML file can of course be opened in Visual Studio for editing, you just require the SharePoint 2010 dlls :-)..."

http://www.wictorwilen.se/Post/Creating-SharePoint-2010-workflows-with-Visio-2010.aspx

and a bit more here:

http://www.visguy.com/2009/08/10/visio-2010-sharepoint-workflows/

Office 2010 SharePoint Designer Findings…

Near as I can tell from the beta, you can't do anything with it unless you've got it hooked up to a SharePoint 2010 Portal. But who's got one of those? Anyway, until Portal 2010 becomes more widely available for testing, SPD 2010 is a useless download of bits…