This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Care Provision: Care Plan 2007 DSTU Feedback"
Jump to navigation
Jump to search
Brett.esler (talk | contribs) |
Brett.esler (talk | contribs) |
||
(2 intermediate revisions by the same user not shown) | |||
Line 10: | Line 10: | ||
* Require '''ObservationGoal.statusCode''' - tracking of goal status | * Require '''ObservationGoal.statusCode''' - tracking of goal status | ||
* '''PlannedCare''' no way to represent a delayed action e.g. perform test 7 days after administering medication | * '''PlannedCare''' no way to represent a delayed action e.g. perform test 7 days after administering medication | ||
+ | |||
+ | |||
+ | [[File:CarePlanDSTU.jpg|700px]] |
Latest revision as of 05:56, 27 June 2011
Care Plan REPC_RM000200UV DSTU
Issues determined as part of trial use:
- Require author participation on PlannedCare - allow original author to be identified
- Require all PlannedCare clinical elements to support effectiveTime (GTS) - allows PIVL (Periodic Interval) and EIVL (Event Related Interval) e.g every 6 months
- Require all PlannedCare clinical elements to support title (ST) - concise details of planned act
- Criterion was an issue with the RIM/Vocab at the time (EVN.CRT now deprecated); can use Act.isCriterionInd attribute and rquire expansion to include (ObservationCriterion, SubstanceAdministrationCriterion, ProcedureCriterion, EncounterCriterion, ActCriterion)
- Require all DefinedCare clinical elements to support effectiveTime (GTS) - as per PlannedCare above
- Require ObservationGoal.id - tracking of goals by reference
- Require ObservationGoal.statusCode - tracking of goal status
- PlannedCare no way to represent a delayed action e.g. perform test 7 days after administering medication