Goal of the transaction below: "Always create a new lab Observation, and also -- if needed -- create a new Patient to serve as the subject of that observation".
listings = []; | |
$.each($("span.txt"), function(i, l){ | |
var url = $("a", l).attr("href"); | |
var title = $("a", l).text(); | |
var posted = $("time", l).attr("datetime"); | |
var price = $("span.price", l).text(); | |
var neighborhood = $("span.pnr small", l).text(); | |
var br = $("span.housing", l).text(); | |
var fees = $("a.gc", l).text(); | |
listings.push([title, url, posted, price, neighborhood, fees].join("\t")); |
Enable a common set of scopes that can be used across UMA-based authorization and "vanilla OAuth 2.0" authorization in a consistent way. In particular, support a model where apps know which permissions they'll need and can get authorized, up-front, with all of those permissions explicitly (rather than attempting a FHIR operation, engaging in an UMA flow... and then repeating this process each time the app needs to issue a new query against the patient's clinical record). Effectively it's a way to standardize the logic by which an UMA resource server knows which scopes to register when it creates
for rev in `git rev-list --reverse --all`; | |
do | |
git checkout $rev; | |
COUNT=$(cat trunk/source/fhir.ini trunk/build/source/fhir.ini | awk '/^\s*$/{flag=0}flag && /=/;/\[resources\]/{flag=1}' | wc -l); | |
DATE=$(git log -1 --date=iso --format=%ai .); | |
echo "$DATE $COUNT" >> /tmp/fhir_counts; | |
echo "$DATE $COUNT"; | |
done |
{ | |
"resourceType": "StructureDefinition", | |
"id": "oauth-uris", | |
"url": "http://fhir-registry.smarthealthit.org/StructureDefinition/oauth-uris", | |
"name": "OAuth Endpoint URIs", | |
"publisher": "SMART Health IT", | |
"contact": [ { | |
"telecom": [ { | |
"system": "other", | |
"value": "http://smarthealthit.org" |
Health IT Standards present an evolving landscape. Aspects of healthcare data exchange are working today, but clincians and patients face serious challenges on the ground. There are multiple perspectives about the best path forward.
Under the Meaningful Use Stage 2 incentive program, 2014-certified EHRs enable exchange of clinical data via the Consolidated CDA document format. Two key patterns are: exchange among clinicians
--> POST / HTTP/1.1 | |
--> User-Agent: Faraday v0.9.2 | |
--> Authorization: [redacted] | |
--> Travis-Repo-Slug: hl7-fhir/fhir-svn | |
--> Content-Type: application/x-www-form-urlencoded | |
--> Accept-Encoding: gzip;q=1.0,deflate;q=0.6,identity;q=0.3 | |
--> Accept: */* | |
--> Connection: close | |
--> Host: fhir.me:8999 | |
--> Content-Length: 12261 |