Hey. We have a release candidate of the Clinical Meteor track online. You can run it using the following:
meteor --release clinical:METEOR@1.1.3-rc4
Also, there’s a new github repository where we’re storing the official packages:
Testing is still going in, but will probably finalize with StarryNight/Nightwatch for Validation tests; and clinical:verification for Verification tests (currently forked from munit; but probably getting upgraded to practicalmeteor:mocha). Package and application testing will be using Travis CI by default.
The package manifest currently includes the following; but will grow quite a bit more in the upcoming few months.
"accounts-base":"1.2.0",
"accounts-password":"1.1.1",
"aldeed:autoform":"5.5.1",
"aldeed:collection2":"2.5.0",
"aldeed:http":"0.2.2",
"aldeed:simple-schema":"1.3.3",
"aldeed:template-extension":"3.4.3",
"autopublish":"1.0.3",
"autoupdate":"1.2.1",
"awatson1978:fonts-helveticas":"1.0.4",
"base64":"1.0.3",
"binary-heap":"1.0.3",
"blaze":"2.1.2",
"blaze-tools":"1.0.3",
"boilerplate-generator":"1.0.3",
"callback-hook":"1.0.3",
"cfs:http-methods":"0.0.30",
"check":"1.0.5",
"clinical:accounts-housemd":"1.1.0",
"clinical:active-entry":"1.2.5",
"clinical:active-questionnaire":"1.0.7",
"clinical:active-record":"1.0.12",
"clinical:barcode":"3.0.1",
"clinical:collaborations":"2.1.2",
"clinical:collaborations-ui":"2.1.6",
"clinical:env":"3.1.5",
"clinical:extended-api":"2.0.3",
"clinical:json2json":"0.0.1",
"clinical:keybindings":"1.0.8",
"clinical:migrations":"0.8.7",
"clinical:modals":"1.0.5",
"clinical:overlays":"2.1.4",
"clinical:study-picklist":"1.0.5",
"clinical:user-model":"1.2.0",
"clinical:users-picklist":"1.0.5",
"coffeescript":"1.0.6",
"ddp":"1.1.0",
"deps":"1.0.7",
"digilord:faker":"1.0.7",
"ejson":"1.0.6",
"email":"1.0.6",
"fastclick":"1.0.3",
"fortawesome:fontawesome":"4.4.0",
"gadicohen:prism":"1.0.4",
"geojson-utils":"1.0.3",
"grove:less":"0.1.1",
"html-tools":"1.0.4",
"htmljs":"1.0.4",
"http":"1.1.0",
"id-map":"1.0.3",
"insecure":"1.0.3",
"iron:controller":"1.0.8",
"iron:core":"1.0.8",
"iron:dynamic-template":"1.0.8",
"iron:layout":"1.0.8",
"iron:location":"1.0.9",
"iron:middleware-stack":"1.0.10",
"iron:router":"1.0.9",
"iron:url":"1.0.9",
"jquery":"1.11.3_2",
"launch-screen":"1.0.2",
"livedata":"1.0.13",
"localstorage":"1.0.3",
"logging":"1.0.7",
"matb33:collection-hooks":"0.7.15",
"meteor":"1.1.6",
"meteor-platform":"1.2.2",
"minifiers":"1.1.5",
"minimongo":"1.0.8",
"mobile-status-bar":"1.0.3",
"momentjs:moment":"2.10.6",
"mongo":"1.1.0",
"mongo-livedata":"1.0.8",
"mousetrap:mousetrap":"1.4.6_1",
"natestrauser:jquery-scrollto":"1.4.7",
"npm-bcrypt":"0.7.8_2",
"observe-sequence":"1.0.6",
"ordered-dict":"1.0.3",
"pfafman:font-awesome-4":"4.2.0_4",
"photonic:active-record-core":"0.0.3",
"photonic:active-record-footer":"0.0.5",
"photonic:active-record-header":"0.0.4",
"photonic:active-users-core":"0.0.3",
"photonic:active-users-table":"0.0.3",
"photonic:glass-ui":"0.2.6",
"photonic:no-select-everything":"0.1.0",
"random":"1.0.3",
"reactive-dict":"1.1.0",
"reactive-var":"1.0.5",
"reload":"1.1.3",
"retry":"1.0.3",
"routepolicy":"1.0.5",
"service-configuration":"1.0.4",
"session":"1.1.0",
"sha":"1.0.3",
"socialize:base-model":"0.2.3",
"socialize:server-time":"0.1.2",
"spacebars":"1.0.6",
"spacebars-compiler":"1.0.6",
"srp":"1.0.3",
"standard-app-packages":"1.0.5",
"starrynight:dropdatabase":"0.0.3",
"templating":"1.1.1",
"tmeasday:publish-with-relations":"0.2.0",
"tracker":"1.0.7",
"ui":"1.0.6",
"underscore":"1.0.3",
"url":"1.0.4",
"webapp":"1.2.0",
"webapp-hashing":"1.0.3",
"yasaricli:slugify":"0.0.7"
Initial package manifest is being generated from CKCC, a rewrite of the ClinicalTrials app, and available here. The CKCC code will eventually get merged back into the ClinicalTrials application, and is under heavy development. So consider it an early-access version of one of the demo apps.
As SocialHealthRecord and ChecklistManifesto go online, we’ll be reusing these specific package versions; and be adding packages that are confirmed to work with the track.
Lastly, it looks like it’s going to be easier to upgrade to 1.2.x than expected, so it’s fairly likely that we’re going to make that upgrade before the official release happens at the end of the year.
Feedback and thoughts welcome. 
Abigail