Difference between revisions of "Straw Man2"
From IHE-UK
(Fleshed out) |
|||
| Line 11: | Line 11: | ||
!Suggested XDS implementation | !Suggested XDS implementation | ||
|- | |- | ||
| − | | Patient demographics | + | | Patient demographics (global and local IDs) |
| Standard XDS usage - Patient ID and source Patient info | | Standard XDS usage - Patient ID and source Patient info | ||
|- | |- | ||
Revision as of 13:41, 7 August 2014
This schema is based on minimal standard metadata, with additional name value pairs in the Reference ID fields to hold some or all of the following:
- Specialties (hierarchical and potentially multiple)
- References to "content" - such as PRSB sub-headings
- Pathway ID
- Episode, spell IDs etc. (as used in mental health/community)
| Generic Requirement | Suggested XDS implementation |
|---|---|
| Patient demographics (global and local IDs) | Standard XDS usage - Patient ID and source Patient info |
| Overall Codec Document Classification | Class Code (source TBD) & Type Code (from SNOMED "correspondence document type" subset) |
| Author(s)& Authenticator | Standard XDS representation, including person (name), role, specialty and institution & Legal Authenticator |
| Context * Environment | Healthcare Facility Type Code & Practice Setting Code |
| Human readable summary for visual scanning | Title & Comments |
| Low level technical representation, location, Date time etc. |
|
| Confidentiality requirements | Confidentiality Code |
| Specialty-specific codes (e.g. modality/procedure/body part for radiology, or operation code for surgery) | EventCodeList |
| Speciality/"treatment function code"/"folder" - see note 1. | ReferenceIdList with multiple key-value pairs (in reality, coded values) - e.g.
|
Administrative "links" - e.g.
|
ReferenceIdList with key-value pairs (in reality, coded values)- e.g.
|
| Contents included - see note 2. | ReferenceIdList with multiple key-value pairs (in reality, coded values)- e.g.
|
Notes:
- 1 - Specialty
- This is emerging as one of the most important search fields, and as shown in DocMan may need to have a different level of granularity for different users.
- 2 - Content
- This would share codes with the PRSB headings/sub-headings to allow a user to locate a document which contains a particular type of data, irrespective of the document's nominal type.
