ewoutkramer

--- !clarkevans.com/^invoice
invoice: 34843
date   : 2001-01-23
bill-to: &id001
    given  : Chris
    family : Dumars
    address:
        lines: |
            458 Walkman Dr.
            Suite #292

ewoutkramer

NamingSystem

Profile

Conformance

ExtensionDefinition

DataElement

SearchParameter

OperationDefinition

ValueSet

ewoutkramer

Interpretation of ElementDefinition in different contexts

The pseudo-datatype ElementDefinition is used both in StructureDefinition and ExtensionDefinition, and even within those resources, the way its elements are to be used and interpreted depend on the context where ElementDefinition used.

Common properties

• short, formal, comments, requirements, synonym can be used in any context to convey a change to the interpretation of the constrained element as compared to the base definition.
• condition and constraint may be used in all contexts
• mapping may be used in all contexts

First (root) element in a structure

ewoutkramer

<element>
    <path value="DiagnosticReport.diagnostic[x]"/>
    <slicing>
        <!-- because I'm slicing on type,right? -->
        <discriminator value="type"/>
        <ordered value="false"/>
        <rules value="closed"/>
    </slicing>
    <!-- both dateTime and Period are allowed. There are no constraints on dateTime. However, if you use a Period, you have to provide a begin time ánd end time -->
    <definition>

ewoutkramer

Ewout's Chicago WGM 2014 notes

PA

1. Want to rename the Schedule datatype, is that ok with core team?
2. Are our resource proposals we sent to FMG in May acceptable? Where can we find feedback?
3. When is the QA period for DSTU2?
4. PA has finished making a ServiceDeliveryLocation profile on Location
5. What is balloted in May? Leftovers from the january ballot? Can we still do major changes after january WGM?

ewoutkramer

Medical Device Workflows in FHIR

Medical device workflow are rich and complex. This design attempts to factor the domain into a minimal set of components that can be combined to produce useful systems. It's self-consciously naïve, but it should serve as a seed for discussion.

A few assumptions and a sketch

• Any device can be online all the time, and can act as a FHIR server -- possible all on its own, or possibly with the help of a proxy/manager/facade component that "fronts for" the device. (Communication between the device and its manager occurs using any mechanism necessary; but the components below be useful for such internal communication, too.)

(EK: The assumption that a device can act as a server, won't that preclude the use of our resources by less powerful devices? I'm just thinking about smaller worn devices, etc. Maybe just posting results somewhere is the max we can expect from them)

ewoutkramer

using System;
using System.Collections.Generic;
using System.Linq;
using System.Security.Cryptography;
using System.Security.Cryptography.X509Certificates;
using System.Security.Cryptography.Xml;
using System.Text;
using System.Threading.Tasks;
using System.Xml;
using System.Xml.Linq;

ewoutkramer

Remarks:

#### In credits.html
>The Management board is Lorraine Constable, Jean Duteau, Hugh Glover, David Hay, Lloyd McKenzie, John Moehrke, Brian Pech, John Quinn and Ron Parker

I think this list is outdated

#### In summary.html
(nothing)

ewoutkramer

{
    "resourceType": "Patient",
    "identifier": [{
        "label": "MRN",
        "period": {"start": "2001-05-06"},
        "assigner": {"display": "Acme Healthcare"},
        "use": "usual",
        "system": "urn:oid:1.2.36.146.595.217.0.1",
        "value": "12345"
    }],