<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <p><br>
    </p>
    <p>The RM has been changed (see
      <a class="moz-txt-link-freetext" href="https://openehr.atlassian.net/browse/SPECRM-52">https://openehr.atlassian.net/browse/SPECRM-52</a>) and the change
      will be included in the next release 1.0.4, for which we will
      determine a date at the SEC meeting end of this month.</p>
    <p>I would suggest that the archetypes be reverted to 'persistent'
      at some point soon after that.<br>
    </p>
    <p>- thomas<br>
    </p>
    <br>
    <div class="moz-cite-prefix">On 08/07/2017 03:02, Heather Leslie
      wrote:<br>
    </div>
    <blockquote
cite="mid:ME1PR01MB11390D33F4855ED8E0B5EFB3EAAB0@ME1PR01MB1139.ausprd01.prod.outlook.com"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=windows-1252">
      <meta name="Generator" content="Microsoft Word 15 (filtered
        medium)">
      <!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]-->
      <style><!--
/* Font Definitions */
@font-face
        {font-family:"Cambria Math";
        panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
        {font-family:Calibri;
        panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0cm;
        margin-bottom:.0001pt;
        font-size:11.0pt;
        font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:purple;
        text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
        {mso-style-name:msonormal;
        mso-margin-top-alt:auto;
        margin-right:0cm;
        mso-margin-bottom-alt:auto;
        margin-left:0cm;
        font-size:11.0pt;
        font-family:"Calibri",sans-serif;}
span.EmailStyle18
        {mso-style-type:personal-reply;
        font-family:"Calibri",sans-serif;
        color:windowtext;}
.MsoChpDefault
        {mso-style-type:export-only;
        mso-fareast-language:EN-US;}
@page WordSection1
        {size:612.0pt 792.0pt;
        margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
        {page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
      <div class="WordSection1">
        <p class="MsoNormal"><span style="mso-fareast-language:EN-US">Hi
            Pablo,<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span style="mso-fareast-language:EN-US">This
            is a longstanding issue and workaround.<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span style="mso-fareast-language:EN-US">See
            the last paragraph in 'Use' for each of the COMPOSITIONS
            that theoretically should be persistent but have been
            modelled as an event:
            <o:p></o:p></span></p>
        <p class="MsoNormal"><i><span style="mso-fareast-language:EN-US">"This
              archetype is usually managed as a persistent list, however
              there are situations where the list may be used within
              episodic care and require additional attributes such as
              context etc to enable accurate recording. The openEHR
              reference model currently only allows context to be
              recorded within Event-based COMPOSITION archetypes. As a
              result, this archetype has been modelled as an Event,
              rather than Persistent, COMPOSITION, to allow for
              flexibility so that some clinical systems can safely
              manage Problem lists for episodes of care, while others
              will choose to implement this COMPOSITION to act in a
              persistent manner."<o:p></o:p></span></i></p>
        <p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span style="mso-fareast-language:EN-US">Until
            there is a change in the RM to cater for this use case we
            are a bit stuck!<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span style="mso-fareast-language:EN-US">Regards<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
      </div>
    </blockquote>
    <br>
  </body>
</html>