FHIR设计之痛

[wanghaisheng]

The biggest thing about interfacing is that one way or another you want to get ‘random access’ to 100% of the data contained in any given application.
http://www.interfaceware.com/blog/fhir-iguana-profit/

[wanghaisheng]

[15/4/16 下午8:00:54] wanghaisheng: 3 Meta.lastUpdated is used to When the resource last changed. but how to record When the resource is created??
[15/4/16 下午8:01:17] Brian Postlethwaite: that's the value on the oldest version
[15/4/16 下午8:49:56] wanghaisheng: on the oldest version ??
[15/4/16 下午9:00:45] Brian Postlethwaite: For example, for /Patient/1, iterate over the history bundle /Patient/1/_history, and the meta.lastmodified is when it was created
[15/4/16 下午9:01:28] Brian Postlethwaite: This assumes that the server is retaining the whole version history for the resource too.

[wanghaisheng]

meta.lastUpdated inconsistency between http://hl7-fhir.github.io/http.html#create 2.1.0.13 create and
http://hl7-fhir.github.io/resource-definitions.html#Resource.meta

The request body SHALL be a FHIR Resource without an id element (this is the only case where a resource exists without an id element). If the request body includes a meta, the server SHALL ignore the existing versionId and lastUpdated values. The server SHALL populate the meta.versionId and meta.lastUpdated with the new correct values. Servers are allowed to review and alter the other metadata values, but SHOULD refrain from doing so (see metadata description for further information). 

This value is always populated except when the resource is first being created. The server / resource manager sets this value; what a client provides is irrelevant.

the sencond one for me when create resource we will not populate this value.