References/Resource Category: Difference between revisions

The Django model is just storage. The behaviour you code against lives in the Pydantic resource specs in <code>care/emr/resources/resource_category/</code>: the <code>resource_type</code> enum, the <code>MonetaryComponent</code> shape behind the <code>*_monetary_components</code> JSON fields, slug validation, and the split between read and write schemas. Several model fields are opaque <code>JSONField</code>s whose real structure exists only in the specs — see [[#resource-specs-api-schema|Resource specs (API schema)]].

== Models ==

{{Field|model=ResourceCategory|section=Tree structure|name=parent|type=FK → emr.ResourceCategory (CASCADE)|notes=Self-reference to the parent node; nullable. <code>related_name=&quot;children&quot;</code>. <code>__exclude__</code>d from spec serialization — written via slug lookup, read via <code>get_parent_json()</code>}}

{{Field|model=ResourceCategory|section=Tree structure|name=is_child|type=BooleanField|notes=Default <code>False</code>. Exposed on write (<code>ResourceCategoryWriteSpec</code>) and read}}

{{Field|model=ResourceCategory|section=Tree structure|name=root_org|type=FK → emr.ResourceCategory (CASCADE)|notes=Self-reference to the root of this node's tree; nullable. <code>related_name=&quot;root&quot;</code>. Not exposed in specs}}

|}

! Notes

{{Field|model=ResourceCategory|section=Charge item monetary components|name=configured_monetary_components|type=JSONField → list[MonetaryComponent] | None|notes=Components configured directly on this category}}

|}

* Monetary-component propagation runs through Celery, so descendants' <code>calculated_monetary_components</code> is eventually consistent after a write.

* Monetary-component fields serialize only for <code>resource_type == &quot;charge_item_definition&quot;</code>; during merges, component identity rests on the nested <code>code.system</code> + <code>code.code</code> pair.

{{Navbox platform}}