Saturday, August 22, 2009

...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

Sunday, August 16, 2009

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

Thursday, August 13, 2009

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!

Wednesday, August 12, 2009

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/


Tuesday, August 11, 2009

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…

Sunday, August 9, 2009

NO Brainer: CTMS/EDC on SharePoint. Why fight it? Microsoft’s SharePoint Thrives in the Recession - Bits Blog - NYTimes.com

Microsoft’s SharePoint Thrives in the Recession - Bits Blog - NYTimes.com

Microsoft’s SharePoint Thrives in the Recession
By Ashlee Vance
Hang around at Microsoft’s Redmond, Wash., headquarters for five or ten minutes and someone dressed in khaki pants and a blue shirt is bound to tell you about the wonders of SharePoint — one of the company’s most successful and increasingly controversial lines of software.
Think of SharePoint as the jack-of-all-trades in the business software realm. Companies use it to create Web sites and then manage content for those sites. It can help workers collaborate on projects and documents. And it has a variety of corporate search and business intelligence tools too.
Microsoft wraps all of this software up into a package and sells the bundle at a reasonable price. In fact, the total cost of the bundle often comes in below what specialist companies would charge for a single application in, say, the business intelligence or corporate search fields.
It can’t do everything. Executives at Microsoft will readily admit that the bits and pieces of SharePoint lack the more sophisticated features found in products from specialist software makers.
“We don’t claim we do everything,” said Chris Capossela, a senior vice president at Microsoft. “If we do 50 percent of the functions that these other companies do, but they’re the ones customers really want, that’s fine. The magic is that end users actually like to use the software.”
This strategy seems to have worked even during the recession.
While Microsoft’s Windows sales fell for the first time in history this year, its SharePoint sales have gone up. Microsoft declines to break out the exact sales figures for the software but said that SharePoint broke the $1 billion revenue mark last year and continued to rise past that total this year, making it the hottest selling server-side product ever for the company.
Companies like Ferrari, Starbucks and Viacom have used SharePoint to create their public-facing Web sites and for various other tasks. All told, more than 17,000 customers use SharePoint.
In many ways, SharePoint mimics the strategy Microsoft took with Office by linking together numerous applications into a single unit. This approach appeals to customers looking to save money and also represents a real threat to a variety of business software makers.
Many of these specialists like Cognos, a business intelligence software maker, and Documentum, a content management software maker, have been gobbled up by larger players looking to create their own suites. I.B.M., for example, bought Cognos, while EMC bought Documentum. Other companies like Autonomy, a maker of top-of-the-line corporate search software, remain independent.
Crucially, Microsoft has found a way to create ties between SharePoint and its more traditional products like Office and Exchange. Companies can tweak Office documents through SharePoint and receive information like whether a worker is online or not through tools in Exchange. These links have Microsoft carrying along its old-line software as it builds a more Internet-focused software line.
“SharePoint is saving Microsoft’s Office business even as it paves the way for a new era of Microsoft lock-in,” said Matt Asay, an executive at Alfresco, which makes an open-source content management system. “It is simultaneously the most interesting and dangerous Microsoft technology, and has largely caught its competitors napping.”
Along these lines, Steve Ballmer, Microsoft’s chief executive, has talked about SharePoint as the company’s next big operating system.
Microsoft has managed to undercut even the panoply of open-source companies playing in the business software market by giving away a free basic license to SharePoint if they already have Windows Server. “It’s a brilliant strategy that mimics open source in its viral, free distribution, but transcends open source in its ability to lock customers into a complete, not-free-at-all Microsoft stack - one for which they’ll pay more and more the deeper they get into SharePoint,” Mr. Asay said.
A number of smaller software companies have been eager to piggyback on SharePoint’s success. Based in San Diego, Sharepoint360 provides consulting services and software development help around the product. The company started after employees at a construction company built some Sharepoint applications and decided to market the software to other construction firms.
The start-up has helped construction companies create systems for managing projects, allowing various people to check-in on the progress of a building and keep track of documents tied to the site. It has also expanded beyond the construction area doing work for NASA, Nestle and Toshiba, according to Paul West, a co-founder of SharePoint360.
The company offers to host SharePoint applications for customers. Microsoft too wants to host more software for companies as it moves toward the cloud computing model.
Mr. West recognizes that Microsoft may begin stepping on its partners’ toes. “It may certainly come to pass that they pull the switch,” he said. “That would have implications for us.”
In the meantime, however, Microsoft subsidizes training courses and consulting work for companies like Sharepoint360.
Next year, Microsoft plans to release a new version of the software packed full of more advanced features, including stronger ties to the corporate search technology it acquired in the $1.2 billion purchase of Fast Search and Transfer, a Norwegian start-up.
Best Buy uses the Fast technology today to provide on-the-fly pricing information to customers performing product searches on its Web site.
By making these more sophisticated tools available to customers, Microsoft thinks it can keep pushing niche software makers out of the way and give business people, rather than just the tech folks, a way to work with business applications.
“We believe customers can turn off some of these point solutions,” said Kirk Koenigsbauer, a general manager in Microsoft’s business software group. “With SharePoint, we can deliver a very, very approachable application to end users.”

Saturday, August 8, 2009

FYI: Base SAS: PROC CDISC Field Response Release

Base SAS: PROC CDISC Field Response Release: "SAS Clinical Standards Toolkit"

"In Q3 2009, SAS expects to release a new product called the SAS Clinical Standards Toolkit. The toolkit will provide define.xml creation, SDTM validation, and eventually will cover Health and Life Sciences industry standards support. Upon availability of the toolkit, SAS recommends using the SAS Clinical Standards Toolkit to create define.xml instead of PROC CDISC. The toolkit is in active development with several additional releases planned while PROC CDISC is planned for maintenance only - no new features. The toolkit is a separately orderable component that will be available at no additional charge to SAS customers." -SAS website

PROC CDISC was a myth. I'll belive this one when I see it. -dave

Sunday, August 2, 2009

CDISC enabled InfoPath and SharePoint EDC toolset

Our group has developed the first (that we're aware of) CDISC wrapper technology enabling full "awareness" of CDISC ODM specifications by InfoPath and SharePoint. The technology allows for autogeneration of InfoPath forms by externally defined CDISC ODM XML. Pretty cool. Email me if you want to learn more or would like to help to further define the project.