Difference between revisions of "BodySite FHIR Resource Proposal"
| Line 60: | Line 60: | ||
==Resource appropriateness== | ==Resource appropriateness== | ||
| − | + | meets the following characteristics: | |
| Line 66: | Line 66: | ||
* Represents a concept expected to be tracked with distinct, reliable, unique ids - yes | * Represents a concept expected to be tracked with distinct, reliable, unique ids - yes | ||
* Reasonable for the resource to be independently created, queried and maintained - yes | * Reasonable for the resource to be independently created, queried and maintained - yes | ||
| − | + | <!-- | |
Should | Should | ||
* Declared interest in need for standardization of data exchange</span> | * Declared interest in need for standardization of data exchange</span> | ||
Revision as of 05:38, 8 February 2015
This page documents a Pending FHIR Resource Proposal
Contents
- 1 Proposed Resource Name
- 2 Owning committee name
- 3 Contributing or Reviewing Work Groups
- 4 FHIR Resource Development Project Insight ID
- 5 Scope of coverage
- 6 RIM scope
- 7 Resource appropriateness
- 8 Expected implementations
- 9 Content sources
- 10 Example Scenarios
- 11 Resource Relationships
- 12 Timelines
- 13 gForge Users
Proposed Resource Name
bodysite BodySite
Owning committee name
Orders and Observations
Contributing or Reviewing Work Groups
- Anatomic Pathology
FHIR Resource Development Project Insight ID
pending
Scope of coverage
see Gforge Comment #3600. Summary harmonize representation of bodysite among existing resources using choice of codeableConcept|reference(BodySite). The BodySite resource will define anatomic location with more discrete elements. New resource: Identifier (site), code, with several other concepts.
RIM scope
TBD
Resource appropriateness
meets the following characteristics:
- Represents a well understood, "important" concept in the business of healthcare - see open EHR anatomic location archetype
- Represents a concept expected to be tracked with distinct, reliable, unique ids - yes
- Reasonable for the resource to be independently created, queried and maintained - yes
Expected implementations
TBD
Content sources
open EHR anatomic location archetype and VA has a LEGO that is very close to our BodySite class in QUICK.
Example Scenarios
research studies, monitoring a lesion, oncology, imaging
Resource Relationships
Observation, DiagnosticOrder, Specimen, Condition, Procedure, MedicationAdministration, ( Immunization ), ImagingStudy
Timelines
March 22, 2015
gForge Users
exsting editors for OO, PC, Pharm, Imaging
