This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Difference between revisions of "Archived CPM Technical Corrections"

From HL7Wiki
Jump to navigation Jump to search
Line 23: Line 23:
 
#::CLARIFICATION:  In the US there is an inhaler that is measured by dose that reaches the mouth whereas in Europe exactly the same product is measured at the point the dose leaves the spray.  The values are simiilar but different so there effectivly 2 different strengths which are equivalent if you use common measurement measures.  Hence a need to express measurement point and countrry.  After rethinking this, I believe that I can map this as a characteristic of the ingredient.
 
#::CLARIFICATION:  In the US there is an inhaler that is measured by dose that reaches the mouth whereas in Europe exactly the same product is measured at the point the dose leaves the spray.  The values are simiilar but different so there effectivly 2 different strengths which are equivalent if you use common measurement measures.  Hence a need to express measurement point and countrry.  After rethinking this, I believe that I can map this as a characteristic of the ingredient.
 
#:::DONE: I agree with you, these fine details can be done with those characteristics. [[User:Gschadow|Gunther]] 14:09, 29 November 2010 (UTC)
 
#:::DONE: I agree with you, these fine details can be done with those characteristics. [[User:Gschadow|Gunther]] 14:09, 29 November 2010 (UTC)
 +
 +
 +
'''From the ISO FDIS for 11615'''
 +
 +
''For "Marketing Authorisation" and "Manufacturing Information"''
 +
 +
In A_ProductInformation
 +
 +
2) Facility to use an additional relationship between a CONTRACT act (the Approval) and a Marketing act to be able to describe the local marketing information that accompanies an approval - possibly a "PERT", please?
 +
 +
:OK: We would agree to add an ActRelationship from MarketingAct to Approval meaning that this MarketingAct is happening with the specified Approval. It might be PERT or a better relationship type. [[User:Gschadow|Gunther]] 14:35, 13 September 2011 (EDT)
 +
 +
3) A confidentiality code on the role coming from the Holder participation, to be able to describe the confidentiality of the information about the marketing authorisation holder. 
 +
 +
:OK: This is easy to do, let's do it. [[User:Gschadow|Gunther]] 22:12, 11 September 2011 (UTC)
  
 
=== R_Substance (POCP_RM080300UV) ===
 
=== R_Substance (POCP_RM080300UV) ===

Revision as of 19:08, 9 November 2011

R_ProductListed (POCP_RM010100UV)

Completed Items

  1. There are a number of Marketing Authorization Dates: First Authorization Date, Renewal Date, Variation Date, Withdrawal Date, Expiry Date. This can be solved by providing a recursive COMP relationship from an authorization to itself.
    DONE Gunther 16:33, 17 November 2010 (UTC)
  2. Each Marketing Authorization produces a GTIN. Provide a SubjectOf shadow from IdentifiedEntity.
    DONE Gunther 16:33, 17 November 2010 (UTC)
  3. IdentifiedEntity needs an effectiveTime
    DONE Gunther 16:33, 17 November 2010 (UTC)
  4. SubjectOf needs a time to indicate when the relevant product information took effect
    QUESTION: such time range would be provided by the connected Act, wouldn't it?
    DONE: My thought was that the effectiveTime of the document could be different from the time when it was attached to the product. But now that I look at it, I don't think that distinction makes sense. --Jduteau 23:06, 18 November 2010 (UTC)
  5. We need to indicate the dose form and the product classification that the marketing authorization pertains to.
    QUESTION: that is already supported because the Approval is connected to a Role whose player Entity has a dose form and can have classifications. Gunther 00:51, 18 November 2010 (UTC)
    CLARIFICATION: the authorization pertains to a specific form and classification. I'm unsure which Role you are referring to as the one with ProductEstablishment doesn't let me detail this.
    DONE: Relates to a specific product with form, etc. all part of the product description. Now, if you say the authorization relates to a "classification" then I think you really mean "indication", or "purpose" for which the product is approved. Currently this is held together by the product document, the label, that is approved. I have added the subjectOf participation to the specializedKind role. Gunther 14:09, 29 November 2010 (UTC)
  6. We need to have the address of the governing agency address.
    DONE Gunther 00:51, 18 November 2010 (UTC)
  7. How to tie the Marketing Authorization Procedure to the marketing authorization.
    ANSWER: the procedure may be reflected in the Approval.code, as it is in the U.S. or you might use the new Approval components to represent these procedures and other smaller actions.
  8. How do we indicate the point and country where a measurement was made.
    ANSWER: ingredient strength is connected to a product and if the strength is different, then it is a different product. The country-specificity can be done with the Approval act.
    CLARIFICATION: In the US there is an inhaler that is measured by dose that reaches the mouth whereas in Europe exactly the same product is measured at the point the dose leaves the spray. The values are simiilar but different so there effectivly 2 different strengths which are equivalent if you use common measurement measures. Hence a need to express measurement point and countrry. After rethinking this, I believe that I can map this as a characteristic of the ingredient.
    DONE: I agree with you, these fine details can be done with those characteristics. Gunther 14:09, 29 November 2010 (UTC)


From the ISO FDIS for 11615

For "Marketing Authorisation" and "Manufacturing Information"

In A_ProductInformation

2) Facility to use an additional relationship between a CONTRACT act (the Approval) and a Marketing act to be able to describe the local marketing information that accompanies an approval - possibly a "PERT", please?

OK: We would agree to add an ActRelationship from MarketingAct to Approval meaning that this MarketingAct is happening with the specified Approval. It might be PERT or a better relationship type. Gunther 14:35, 13 September 2011 (EDT)

3) A confidentiality code on the role coming from the Holder participation, to be able to describe the confidentiality of the information about the marketing authorisation holder.

OK: This is easy to do, let's do it. Gunther 22:12, 11 September 2011 (UTC)

R_Substance (POCP_RM080300UV)

Completed Items

  1. How to indicate the Gene and the specific Gene element that a Substance is derived from?
    ANSWER: IdentifiedSubstance - productOf - DerivationProcess - interactor - IdentifiedSubstance Gunther 00:51, 18 November 2010 (UTC)
    DONE --Jduteau 23:07, 18 November 2010 (UTC)
  2. We have a status and domain of names.
    ANSWER: for domain: NamedEntity - subjectOf - Policy Gunther 00:51, 18 November 2010 (UTC)
    QUESTION: for "status", what are those statuses?
    CLARIFICATION: current, alternate, superceded
    DONE: The specification of what name you need to use under what circumstances is carried by the Policy that you can associate with the Identified(Named)Entity role. If these policies are outdated, or say that you can use a name as an alternative or not any more, would all be handled by Policy. Also added statusCode and effectiveTime into NamedEntity and IdentifiedEntity roles, with a note to use Policy for fine control. Gunther 14:09, 29 November 2010 (UTC)
  3. How to indicate what the amount of a moiety is (mole ratio, weight percent) - this may be similar to the "Amount Type" that is present on all amounts.
    ANSWER: the Role.quantity gives you a ratio, if you put there 1 mol : 1 mol it's a mole-ratio, if you put 1 g : 1 g it's a mass ratio.
    DONE--Jduteau 23:07, 18 November 2010 (UTC)
  4. We need a "SubjectOf" relationship on the NamedEntity to indicate reference information for the names.
    DONE Gunther 00:51, 18 November 2010 (UTC)
  5. Need to provide documentation of a characteristic.
    QUESTION: use case please? Do you mean the subjectOf relationship to Document should be added?
    CLARIFICATION: Yes, there is a need to provide the reference documentation for a characteristic value, so subjectOf relationship to Document.
    DONE Gunther 14:09, 29 November 2010 (UTC)
  6. We have processSteps that have sub-processSteps. SubstanceSpecification does not allow this.
    DONE Gunther 00:51, 18 November 2010 (UTC)
  7. There needs to be a way to link characteristics to each other - either as a grouping of related characteristics or as a parent/child relationship.
    QUESTION: It's easy to add this, but there should be at least one use case. What is it?
    CLARIFICATION: I have a Protein Substance that has information about the sequence. There are characteristics that are all about the sequence. As well, each sequence has a number of sub-units and each sub-unit has a number of characteristics. So it would be nice to tie all of the sub-unit characteristics together and I believe that it is necessary to indicate that each subunit set pertains to the sequence.
    ANSWER: Subunits are different Moieties. You put characteristics onto the molecular part that they pertain to, not on the higher order molecular complex. So, it is actually good that you do not have these characteristics structures, because they make you focus on modeling the molecule, not the information about it. Gunther 14:09, 29 November 2010 (UTC)
  8. Many codes have a status and change date of the code.
    QUESTION: which codes? the "last change date" is a database-ism that does not really do much, in most cases you can refer to the Document that contains the change if you wanted to.
  9. R_SubstancePresence - the scoper is not actually attached to the choice box.
    DONE Gunther 12:49, 3 December 2010 (UTC)
  10. Need to provide documentation of the derivation process - need a link to Document.
    DONE Gunther 12:49, 3 December 2010 (UTC