Add 'episodic' type to COMPOSITION.category

Description

See PRs for description.

Activity

Show:
Bjørn Næss
July 15, 2020, 8:25 AM

The “contextual” is kind of interesting. IMHO is episodic a kind of contextual scope for data. Episodic is about a temporal organisation like a episode of care or a contact period .

It could be that we want the more generic contextual for this attribute?

Ian McNicoll
July 16, 2020, 1:36 PM

We did bounce this around already I would probably gently prefer ‘contextual' but the broad preference seemed to be to stick with 'episodic’ on the basis that even if the boundary is actually a context like a care pathway, rather than an episode of care, the persistence of the data is episodic i.e timebound e.g maintain this problem list for Pathway X until X comes to and and then refresh for any subsequent episodes.

?? Your thoughts

Bjørn Næss
September 21, 2020, 10:27 AM
Edited

Suggestion:
What if we don’t add a new category, and define a new attribute in the RM to tell what context the persistence is about.

The default value is persistent within the EHR.
Then we add the possibility to add a terminology which defines the contextual persistence semantic as i.e. a DV_CODED_TEXT with values like episode of care, periode of care, referral, a surgery, etc.

Persistence will be defined different in the systems and applications. Thus it’s needed to leave the different scopes to the application.

Ian McNicoll
September 21, 2020, 1:54 PM

“Persistence will be defined different in the systems and applications. Thus it’s needed to leave the different scopes to the application.“

Agreed but that’s why I’m not sure that having a ‘flavours of persistence’ attribute takes us much further - I can tag it as ‘period of care’ but how that is actually defined and implemented will be very context/application-specific, so in terms of documenting the behaviour vs. ‘just ‘episodic’ I’m not sure it takes us much further.

Let's find out from other CDR implementers how they are using/enforcing ‘persistent’ right now. I’m not totally opposed to your suggestion!! We could do both, of course - add ‘episodic/contextual’ and a new attribute for the reason.

Perhaps we should just vote on it.

Thomas Beale
September 28, 2020, 3:10 PM

I think does have a useful point here, but I’m inclined to finish this CR as originally envisaged, even if it turns out a) implementers don’t use ‘episodic’ much in the end and/or b) we decide we want some extra ‘temporal_context’ attribute added.

The mere fact that it is not obvious now means that we don’t have enough hard evidence or more solid model idea to propose.

Reporter

Sebastian Iancu

Raised By

Pablo Pazos

Components

Affects versions

Configure