Executive summary
inferno-framework/fhir_models falls short of our standard for production because 13 files are no longer known to anyone active in the project and we found no recorded design decisions and no architecture document or diagram. It scores 53.6 out of 100 and is rated Adequate, and five of its six critical findings are security problems.
Maturity, at 42.6, is the weakest lens and counts most in the score. The best first step is having someone learn and document the 13 files no active contributor knows, worth about 10.4 points. Recording design decisions is another step, worth about 8.6 points. Raising Maturity to 70 would lift the score to about 62.0.
Two known security holes in the packages the code depends on can be used by attackers. Two pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with, and one password or key is open to anyone who can read the repository. Updating the vulnerable packages, pinning each tool to an exact version and replacing the exposed password or key would close these risks.
The product code is 78,833 lines, about €80,000 to rebuild.
If Maturity rose from 42.6 to 70, the lowest score rated Strong, the score would rise from 53.6 to about 62.0.
Rebuild cost: about €80,000 · Estimate
| Cost to rebuild | €27,000 to €130,000, for 444 to 1,410 hours of work, about 0.6 person-years for 1 to 2 engineers |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 54. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Medium: 78,833 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture: which parts of the code depend on which
| uses → | 1 FHIR | 2 FHIR.Generator | 3 FHIR.R4 | 4 FHIR.R4B | 5 FHIR.R5 | 6 FHIR.CommonDefinitions | 7 FHIR.R4.Account | 8 FHIR.R4.ActivityDefinition | 9 FHIR.R4.AdverseEvent | 10 FHIR.R4.AdverseEvent.SuspectEntity | 11 FHIR.R4.AllergyIntolerance | 12 FHIR.R4.Appointment | 13 FHIR.R4.AuditEvent | 14 FHIR.R4.AuditEvent.Agent | 15 FHIR.R4.AuditEvent.Entity | 16 FHIR.R4.BiologicallyDerivedProduct | 17 FHIR.R4.Bundle | 18 FHIR.R4.Bundle.Entry | 19 FHIR.R4.CapabilityStatement | 20 FHIR.R4.CapabilityStatement.Messaging | 21 FHIR.R4.CapabilityStatement.Rest | 22 FHIR.R4.CapabilityStatement.Rest.Resource | 23 FHIR.R4.CarePlan | 24 FHIR.R4.CarePlan.Activity | 25 FHIR.R4.CareTeam | 26 FHIR.R4.CatalogEntry | 27 FHIR.R4.ChargeItem | 28 FHIR.R4.ChargeItemDefinition | 29 FHIR.R4.ChargeItemDefinition.PropertyGroup | 30 FHIR.R4.Claim | 31 FHIR.R4.Claim.Item | 32 FHIR.R4.Claim.Item.Detail | 33 FHIR.R4.ClaimResponse | 34 FHIR.R4.ClaimResponse.AddItem | 35 FHIR.R4.ClaimResponse.AddItem.Detail | 36 FHIR.R4.ClaimResponse.Item | 37 FHIR.R4.ClaimResponse.Item.Detail | 38 FHIR.R4.ClinicalImpression | 39 FHIR.R4.CodeSystem | 40 FHIR.R4.CodeSystem.Concept |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 FHIR | ||||||||||||||||||||||||||||||||||||||||
| 2 FHIR.Generator | 2 | |||||||||||||||||||||||||||||||||||||||
| 3 FHIR.R4 | 580 | |||||||||||||||||||||||||||||||||||||||
| 4 FHIR.R4B | 571 | |||||||||||||||||||||||||||||||||||||||
| 5 FHIR.R5 | 643 | |||||||||||||||||||||||||||||||||||||||
| 6 FHIR.CommonDefinitions | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 7 FHIR.R4.Account | 6 | 2 | ||||||||||||||||||||||||||||||||||||||
| 8 FHIR.R4.ActivityDefinition | 6 | 2 | ||||||||||||||||||||||||||||||||||||||
| 9 FHIR.R4.AdverseEvent | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 10 FHIR.R4.AdverseEvent.SuspectEntity | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 11 FHIR.R4.AllergyIntolerance | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 12 FHIR.R4.Appointment | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 13 FHIR.R4.AuditEvent | 9 | 3 | ||||||||||||||||||||||||||||||||||||||
| 14 FHIR.R4.AuditEvent.Agent | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 15 FHIR.R4.AuditEvent.Entity | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 16 FHIR.R4.BiologicallyDerivedProduct | 12 | 4 | ||||||||||||||||||||||||||||||||||||||
| 17 FHIR.R4.Bundle | 6 | 2 | ||||||||||||||||||||||||||||||||||||||
| 18 FHIR.R4.Bundle.Entry | 9 | 3 | ||||||||||||||||||||||||||||||||||||||
| 19 FHIR.R4.CapabilityStatement | 15 | 5 | ||||||||||||||||||||||||||||||||||||||
| 20 FHIR.R4.CapabilityStatement.Messaging | 6 | 2 | ||||||||||||||||||||||||||||||||||||||
| 21 FHIR.R4.CapabilityStatement.Rest | 9 | 3 | ||||||||||||||||||||||||||||||||||||||
| 22 FHIR.R4.CapabilityStatement.Rest.Resource | 9 | 3 | ||||||||||||||||||||||||||||||||||||||
| 23 FHIR.R4.CarePlan | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 24 FHIR.R4.CarePlan.Activity | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 25 FHIR.R4.CareTeam | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 26 FHIR.R4.CatalogEntry | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 27 FHIR.R4.ChargeItem | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 28 FHIR.R4.ChargeItemDefinition | 6 | 2 | ||||||||||||||||||||||||||||||||||||||
| 29 FHIR.R4.ChargeItemDefinition.PropertyGroup | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 30 FHIR.R4.Claim | 27 | 9 | ||||||||||||||||||||||||||||||||||||||
| 31 FHIR.R4.Claim.Item | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 32 FHIR.R4.Claim.Item.Detail | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 33 FHIR.R4.ClaimResponse | 21 | 7 | ||||||||||||||||||||||||||||||||||||||
| 34 FHIR.R4.ClaimResponse.AddItem | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 35 FHIR.R4.ClaimResponse.AddItem.Detail | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 36 FHIR.R4.ClaimResponse.Item | 6 | 2 | ||||||||||||||||||||||||||||||||||||||
| 37 FHIR.R4.ClaimResponse.Item.Detail | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 38 FHIR.R4.ClinicalImpression | 6 | 2 | ||||||||||||||||||||||||||||||||||||||
| 39 FHIR.R4.CodeSystem | 9 | 3 | ||||||||||||||||||||||||||||||||||||||
| 40 FHIR.R4.CodeSystem.Concept | 6 | 2 |
2→1 FHIR.Generator uses FHIR✕
- Connections
- 2 pairs of types, where a type in FHIR.Generator uses a type in FHIR.
- The types involved
FHIR.Generator.Template→FHIR.DeprecateFHIR.Generator.Template→FHIR.Hashable
- Direction
- FHIR.Generator uses FHIR, so a change to FHIR can break FHIR.Generator, while a change to FHIR.Generator can't break FHIR.
- Position
- Below the diagonal: FHIR.Generator uses a module listed above it, which is the healthy direction.
3→1 FHIR.R4 uses FHIR✕
- Connections
- 580 pairs of types, where a type in FHIR.R4 uses a type in FHIR. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
FHIR.R4.Account→FHIR.HashableFHIR.R4.Account→FHIR.JsonFHIR.R4.Account→FHIR.XmlFHIR.R4.ActivityDefinition→FHIR.HashableFHIR.R4.ActivityDefinition→FHIR.JsonFHIR.R4.ActivityDefinition→FHIR.XmlFHIR.R4.Address→FHIR.HashableFHIR.R4.Address→FHIR.JsonFHIR.R4.Address→FHIR.XmlFHIR.R4.AdverseEvent→FHIR.HashableFHIR.R4.AdverseEvent→FHIR.JsonFHIR.R4.AdverseEvent→FHIR.XmlFHIR.R4.Age→FHIR.HashableFHIR.R4.Age→FHIR.JsonFHIR.R4.Age→FHIR.XmlFHIR.R4.AllergyIntolerance→FHIR.HashableFHIR.R4.AllergyIntolerance→FHIR.JsonFHIR.R4.AllergyIntolerance→FHIR.XmlFHIR.R4.Annotation→FHIR.HashableFHIR.R4.Annotation→FHIR.JsonFHIR.R4.Annotation→FHIR.XmlFHIR.R4.Appointment→FHIR.HashableFHIR.R4.Appointment→FHIR.JsonFHIR.R4.Appointment→FHIR.XmlFHIR.R4.AppointmentResponse→FHIR.Hashable
- Direction
- FHIR.R4 uses FHIR, so a change to FHIR can break FHIR.R4, while a change to FHIR.R4 can't break FHIR.
- Position
- Below the diagonal: FHIR.R4 uses a module listed above it, which is the healthy direction.
4→1 FHIR.R4B uses FHIR✕
- Connections
- 571 pairs of types, where a type in FHIR.R4B uses a type in FHIR. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
FHIR.R4B.Account→FHIR.HashableFHIR.R4B.Account→FHIR.JsonFHIR.R4B.Account→FHIR.XmlFHIR.R4B.ActivityDefinition→FHIR.HashableFHIR.R4B.ActivityDefinition→FHIR.JsonFHIR.R4B.ActivityDefinition→FHIR.XmlFHIR.R4B.Address→FHIR.HashableFHIR.R4B.Address→FHIR.JsonFHIR.R4B.Address→FHIR.XmlFHIR.R4B.AdministrableProductDefinition→FHIR.HashableFHIR.R4B.AdministrableProductDefinition→FHIR.JsonFHIR.R4B.AdministrableProductDefinition→FHIR.XmlFHIR.R4B.AdverseEvent→FHIR.HashableFHIR.R4B.AdverseEvent→FHIR.JsonFHIR.R4B.AdverseEvent→FHIR.XmlFHIR.R4B.Age→FHIR.HashableFHIR.R4B.Age→FHIR.JsonFHIR.R4B.Age→FHIR.XmlFHIR.R4B.AllergyIntolerance→FHIR.HashableFHIR.R4B.AllergyIntolerance→FHIR.JsonFHIR.R4B.AllergyIntolerance→FHIR.XmlFHIR.R4B.Annotation→FHIR.HashableFHIR.R4B.Annotation→FHIR.JsonFHIR.R4B.Annotation→FHIR.XmlFHIR.R4B.Appointment→FHIR.Hashable
- Direction
- FHIR.R4B uses FHIR, so a change to FHIR can break FHIR.R4B, while a change to FHIR.R4B can't break FHIR.
- Position
- Below the diagonal: FHIR.R4B uses a module listed above it, which is the healthy direction.
5→1 FHIR.R5 uses FHIR✕
- Connections
- 643 pairs of types, where a type in FHIR.R5 uses a type in FHIR. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
FHIR.R5.Account→FHIR.HashableFHIR.R5.Account→FHIR.JsonFHIR.R5.Account→FHIR.XmlFHIR.R5.ActivityDefinition→FHIR.HashableFHIR.R5.ActivityDefinition→FHIR.JsonFHIR.R5.ActivityDefinition→FHIR.XmlFHIR.R5.ActorDefinition→FHIR.HashableFHIR.R5.ActorDefinition→FHIR.JsonFHIR.R5.ActorDefinition→FHIR.XmlFHIR.R5.Address→FHIR.HashableFHIR.R5.Address→FHIR.JsonFHIR.R5.Address→FHIR.XmlFHIR.R5.AdministrableProductDefinition→FHIR.HashableFHIR.R5.AdministrableProductDefinition→FHIR.JsonFHIR.R5.AdministrableProductDefinition→FHIR.XmlFHIR.R5.AdverseEvent→FHIR.HashableFHIR.R5.AdverseEvent→FHIR.JsonFHIR.R5.AdverseEvent→FHIR.XmlFHIR.R5.Age→FHIR.HashableFHIR.R5.Age→FHIR.JsonFHIR.R5.Age→FHIR.XmlFHIR.R5.AllergyIntolerance→FHIR.HashableFHIR.R5.AllergyIntolerance→FHIR.JsonFHIR.R5.AllergyIntolerance→FHIR.XmlFHIR.R5.Annotation→FHIR.Hashable
- Direction
- FHIR.R5 uses FHIR, so a change to FHIR can break FHIR.R5, while a change to FHIR.R5 can't break FHIR.
- Position
- Below the diagonal: FHIR.R5 uses a module listed above it, which is the healthy direction.
6→1 FHIR.CommonDefinitions uses FHIR✕
- Connections
- 1 pair of types, where a type in FHIR.CommonDefinitions uses a type in FHIR.
- The types involved
FHIR.CommonDefinitions.ClassMethods→FHIR.Deprecate
- Direction
- FHIR.CommonDefinitions uses FHIR, so a change to FHIR can break FHIR.CommonDefinitions, while a change to FHIR.CommonDefinitions can't break FHIR.
- Position
- Below the diagonal: FHIR.CommonDefinitions uses a module listed above it, which is the healthy direction.
6→2 FHIR.CommonDefinitions uses FHIR.Generator✕
- Connections
- 1 pair of types, where a type in FHIR.CommonDefinitions uses a type in FHIR.Generator.
- The types involved
FHIR.CommonDefinitions.ClassMethods→FHIR.Generator.IGLoader
- Direction
- FHIR.CommonDefinitions uses FHIR.Generator, so a change to FHIR.Generator can break FHIR.CommonDefinitions, while a change to FHIR.CommonDefinitions can't break FHIR.Generator.
- Position
- Below the diagonal: FHIR.CommonDefinitions uses a module listed above it, which is the healthy direction.
7→1 FHIR.R4.Account uses FHIR✕
- Connections
- 6 pairs of types, where a type in FHIR.R4.Account uses a type in FHIR.
- The types involved
FHIR.R4.Account.Coverage→FHIR.HashableFHIR.R4.Account.Coverage→FHIR.JsonFHIR.R4.Account.Coverage→FHIR.XmlFHIR.R4.Account.Guarantor→FHIR.HashableFHIR.R4.Account.Guarantor→FHIR.JsonFHIR.R4.Account.Guarantor→FHIR.Xml
- Direction
- FHIR.R4.Account uses FHIR, so a change to FHIR can break FHIR.R4.Account, while a change to FHIR.R4.Account can't break FHIR.
- Position
- Below the diagonal: FHIR.R4.Account uses a module listed above it, which is the healthy direction.
7→3 FHIR.R4.Account uses FHIR.R4✕
- Connections
- 2 pairs of types, where a type in FHIR.R4.Account uses a type in FHIR.R4.
- The types involved
FHIR.R4.Account.Coverage→FHIR.R4.ModelFHIR.R4.Account.Guarantor→FHIR.R4.Model
- Direction
- FHIR.R4.Account uses FHIR.R4, so a change to FHIR.R4 can break FHIR.R4.Account, while a change to FHIR.R4.Account can't break FHIR.R4.
- Position
- Below the diagonal: FHIR.R4.Account uses a module listed above it, which is the healthy direction.
8→1 FHIR.R4.ActivityDefinition uses FHIR✕
- Connections
- 6 pairs of types, where a type in FHIR.R4.ActivityDefinition uses a type in FHIR.
- The types involved
FHIR.R4.ActivityDefinition.DynamicValue→FHIR.HashableFHIR.R4.ActivityDefinition.DynamicValue→FHIR.JsonFHIR.R4.ActivityDefinition.DynamicValue→FHIR.XmlFHIR.R4.ActivityDefinition.Participant→FHIR.HashableFHIR.R4.ActivityDefinition.Participant→FHIR.JsonFHIR.R4.ActivityDefinition.Participant→FHIR.Xml
- Direction
- FHIR.R4.ActivityDefinition uses FHIR, so a change to FHIR can break FHIR.R4.ActivityDefinition, while a change to FHIR.R4.ActivityDefinition can't break FHIR.
- Position
- Below the diagonal: FHIR.R4.ActivityDefinition uses a module listed above it, which is the healthy direction.
8→3 FHIR.R4.ActivityDefinition uses FHIR.R4✕
- Connections
- 2 pairs of types, where a type in FHIR.R4.ActivityDefinition uses a type in FHIR.R4.
- The types involved
FHIR.R4.ActivityDefinition.DynamicValue→FHIR.R4.ModelFHIR.R4.ActivityDefinition.Participant→FHIR.R4.Model
- Direction
- FHIR.R4.ActivityDefinition uses FHIR.R4, so a change to FHIR.R4 can break FHIR.R4.ActivityDefinition, while a change to FHIR.R4.ActivityDefinition can't break FHIR.R4.
- Position
- Below the diagonal: FHIR.R4.ActivityDefinition uses a module listed above it, which is the healthy direction.
9→1 FHIR.R4.AdverseEvent uses FHIR✕
- Connections
- 3 pairs of types, where a type in FHIR.R4.AdverseEvent uses a type in FHIR.
- The types involved
FHIR.R4.AdverseEvent.SuspectEntity→FHIR.HashableFHIR.R4.AdverseEvent.SuspectEntity→FHIR.JsonFHIR.R4.AdverseEvent.SuspectEntity→FHIR.Xml
- Direction
- FHIR.R4.AdverseEvent uses FHIR, so a change to FHIR can break FHIR.R4.AdverseEvent, while a change to FHIR.R4.AdverseEvent can't break FHIR.
- Position
- Below the diagonal: FHIR.R4.AdverseEvent uses a module listed above it, which is the healthy direction.
9→3 FHIR.R4.AdverseEvent uses FHIR.R4✕
- Connections
- 1 pair of types, where a type in FHIR.R4.AdverseEvent uses a type in FHIR.R4.
- The types involved
FHIR.R4.AdverseEvent.SuspectEntity→FHIR.R4.Model
- Direction
- FHIR.R4.AdverseEvent uses FHIR.R4, so a change to FHIR.R4 can break FHIR.R4.AdverseEvent, while a change to FHIR.R4.AdverseEvent can't break FHIR.R4.
- Position
- Below the diagonal: FHIR.R4.AdverseEvent uses a module listed above it, which is the healthy direction.
10→1 FHIR.R4.AdverseEvent.SuspectEntity uses FHIR✕
- Connections
- 3 pairs of types, where a type in FHIR.R4.AdverseEvent.SuspectEntity uses a type in FHIR.
- The types involved
FHIR.R4.AdverseEvent.SuspectEntity.Causality→FHIR.HashableFHIR.R4.AdverseEvent.SuspectEntity.Causality→FHIR.JsonFHIR.R4.AdverseEvent.SuspectEntity.Causality→FHIR.Xml
- Direction
- FHIR.R4.AdverseEvent.SuspectEntity uses FHIR, so a change to FHIR can break FHIR.R4.AdverseEvent.SuspectEntity, while a change to FHIR.R4.AdverseEvent.SuspectEntity can't break FHIR.
- Position
- Below the diagonal: FHIR.R4.AdverseEvent.SuspectEntity uses a module listed above it, which is the healthy direction.
10→3 FHIR.R4.AdverseEvent.SuspectEntity uses FHIR.R4✕
- Connections
- 1 pair of types, where a type in FHIR.R4.AdverseEvent.SuspectEntity uses a type in FHIR.R4.
- The types involved
FHIR.R4.AdverseEvent.SuspectEntity.Causality→FHIR.R4.Model
- Direction
- FHIR.R4.AdverseEvent.SuspectEntity uses FHIR.R4, so a change to FHIR.R4 can break FHIR.R4.AdverseEvent.SuspectEntity, while a change to FHIR.R4.AdverseEvent.SuspectEntity can't break FHIR.R4.
- Position
- Below the diagonal: FHIR.R4.AdverseEvent.SuspectEntity uses a module listed above it, which is the healthy direction.
11→1 FHIR.R4.AllergyIntolerance uses FHIR✕
- Connections
- 3 pairs of types, where a type in FHIR.R4.AllergyIntolerance uses a type in FHIR.
- The types involved
FHIR.R4.AllergyIntolerance.Reaction→FHIR.HashableFHIR.R4.AllergyIntolerance.Reaction→FHIR.JsonFHIR.R4.AllergyIntolerance.Reaction→FHIR.Xml
- Direction
- FHIR.R4.AllergyIntolerance uses FHIR, so a change to FHIR can break FHIR.R4.AllergyIntolerance, while a change to FHIR.R4.AllergyIntolerance can't break FHIR.
- Position
- Below the diagonal: FHIR.R4.AllergyIntolerance uses a module listed above it, which is the healthy direction.
11→3 FHIR.R4.AllergyIntolerance uses FHIR.R4✕
- Connections
- 1 pair of types, where a type in FHIR.R4.AllergyIntolerance uses a type in FHIR.R4.
- The types involved
FHIR.R4.AllergyIntolerance.Reaction→FHIR.R4.Model
- Direction
- FHIR.R4.AllergyIntolerance uses FHIR.R4, so a change to FHIR.R4 can break FHIR.R4.AllergyIntolerance, while a change to FHIR.R4.AllergyIntolerance can't break FHIR.R4.
- Position
- Below the diagonal: FHIR.R4.AllergyIntolerance uses a module listed above it, which is the healthy direction.
12→1 FHIR.R4.Appointment uses FHIR✕
- Connections
- 3 pairs of types, where a type in FHIR.R4.Appointment uses a type in FHIR.
- The types involved
FHIR.R4.Appointment.Participant→FHIR.HashableFHIR.R4.Appointment.Participant→FHIR.JsonFHIR.R4.Appointment.Participant→FHIR.Xml
- Direction
- FHIR.R4.Appointment uses FHIR, so a change to FHIR can break FHIR.R4.Appointment, while a change to FHIR.R4.Appointment can't break FHIR.
- Position
- Below the diagonal: FHIR.R4.Appointment uses a module listed above it, which is the healthy direction.
12→3 FHIR.R4.Appointment uses FHIR.R4✕
- Connections
- 1 pair of types, where a type in FHIR.R4.Appointment uses a type in FHIR.R4.
- The types involved
FHIR.R4.Appointment.Participant→FHIR.R4.Model
- Direction
- FHIR.R4.Appointment uses FHIR.R4, so a change to FHIR.R4 can break FHIR.R4.Appointment, while a change to FHIR.R4.Appointment can't break FHIR.R4.
- Position
- Below the diagonal: FHIR.R4.Appointment uses a module listed above it, which is the healthy direction.
13→1 FHIR.R4.AuditEvent uses FHIR✕
- Connections
- 9 pairs of types, where a type in FHIR.R4.AuditEvent uses a type in FHIR.
- The types involved
FHIR.R4.AuditEvent.Agent→FHIR.HashableFHIR.R4.AuditEvent.Agent→FHIR.JsonFHIR.R4.AuditEvent.Agent→FHIR.XmlFHIR.R4.AuditEvent.Entity→FHIR.HashableFHIR.R4.AuditEvent.Entity→FHIR.JsonFHIR.R4.AuditEvent.Entity→FHIR.XmlFHIR.R4.AuditEvent.Source→FHIR.HashableFHIR.R4.AuditEvent.Source→FHIR.JsonFHIR.R4.AuditEvent.Source→FHIR.Xml
- Direction
- FHIR.R4.AuditEvent uses FHIR, so a change to FHIR can break FHIR.R4.AuditEvent, while a change to FHIR.R4.AuditEvent can't break FHIR.
- Position
- Below the diagonal: FHIR.R4.AuditEvent uses a module listed above it, which is the healthy direction.
13→3 FHIR.R4.AuditEvent uses FHIR.R4✕
- Connections
- 3 pairs of types, where a type in FHIR.R4.AuditEvent uses a type in FHIR.R4.
- The types involved
FHIR.R4.AuditEvent.Agent→FHIR.R4.ModelFHIR.R4.AuditEvent.Entity→FHIR.R4.ModelFHIR.R4.AuditEvent.Source→FHIR.R4.Model
- Direction
- FHIR.R4.AuditEvent uses FHIR.R4, so a change to FHIR.R4 can break FHIR.R4.AuditEvent, while a change to FHIR.R4.AuditEvent can't break FHIR.R4.
- Position
- Below the diagonal: FHIR.R4.AuditEvent uses a module listed above it, which is the healthy direction.
14→1 FHIR.R4.AuditEvent.Agent uses FHIR✕
- Connections
- 3 pairs of types, where a type in FHIR.R4.AuditEvent.Agent uses a type in FHIR.
- The types involved
FHIR.R4.AuditEvent.Agent.Network→FHIR.HashableFHIR.R4.AuditEvent.Agent.Network→FHIR.JsonFHIR.R4.AuditEvent.Agent.Network→FHIR.Xml
- Direction
- FHIR.R4.AuditEvent.Agent uses FHIR, so a change to FHIR can break FHIR.R4.AuditEvent.Agent, while a change to FHIR.R4.AuditEvent.Agent can't break FHIR.
- Position
- Below the diagonal: FHIR.R4.AuditEvent.Agent uses a module listed above it, which is the healthy direction.
14→3 FHIR.R4.AuditEvent.Agent uses FHIR.R4✕
- Connections
- 1 pair of types, where a type in FHIR.R4.AuditEvent.Agent uses a type in FHIR.R4.
- The types involved
FHIR.R4.AuditEvent.Agent.Network→FHIR.R4.Model
- Direction
- FHIR.R4.AuditEvent.Agent uses FHIR.R4, so a change to FHIR.R4 can break FHIR.R4.AuditEvent.Agent, while a change to FHIR.R4.AuditEvent.Agent can't break FHIR.R4.
- Position
- Below the diagonal: FHIR.R4.AuditEvent.Agent uses a module listed above it, which is the healthy direction.
15→1 FHIR.R4.AuditEvent.Entity uses FHIR✕
- Connections
- 3 pairs of types, where a type in FHIR.R4.AuditEvent.Entity uses a type in FHIR.
- The types involved
FHIR.R4.AuditEvent.Entity.Detail→FHIR.HashableFHIR.R4.AuditEvent.Entity.Detail→FHIR.JsonFHIR.R4.AuditEvent.Entity.Detail→FHIR.Xml
- Direction
- FHIR.R4.AuditEvent.Entity uses FHIR, so a change to FHIR can break FHIR.R4.AuditEvent.Entity, while a change to FHIR.R4.AuditEvent.Entity can't break FHIR.
- Position
- Below the diagonal: FHIR.R4.AuditEvent.Entity uses a module listed above it, which is the healthy direction.
15→3 FHIR.R4.AuditEvent.Entity uses FHIR.R4✕
- Connections
- 1 pair of types, where a type in FHIR.R4.AuditEvent.Entity uses a type in FHIR.R4.
- The types involved
FHIR.R4.AuditEvent.Entity.Detail→FHIR.R4.Model
- Direction
- FHIR.R4.AuditEvent.Entity uses FHIR.R4, so a change to FHIR.R4 can break FHIR.R4.AuditEvent.Entity, while a change to FHIR.R4.AuditEvent.Entity can't break FHIR.R4.
- Position
- Below the diagonal: FHIR.R4.AuditEvent.Entity uses a module listed above it, which is the healthy direction.
16→1 FHIR.R4.BiologicallyDerivedProduct uses FHIR✕
- Connections
- 12 pairs of types, where a type in FHIR.R4.BiologicallyDerivedProduct uses a type in FHIR.
- The types involved
FHIR.R4.BiologicallyDerivedProduct.Collection→FHIR.HashableFHIR.R4.BiologicallyDerivedProduct.Collection→FHIR.JsonFHIR.R4.BiologicallyDerivedProduct.Collection→FHIR.XmlFHIR.R4.BiologicallyDerivedProduct.Manipulation→FHIR.HashableFHIR.R4.BiologicallyDerivedProduct.Manipulation→FHIR.JsonFHIR.R4.BiologicallyDerivedProduct.Manipulation→FHIR.XmlFHIR.R4.BiologicallyDerivedProduct.Processing→FHIR.HashableFHIR.R4.BiologicallyDerivedProduct.Processing→FHIR.JsonFHIR.R4.BiologicallyDerivedProduct.Processing→FHIR.XmlFHIR.R4.BiologicallyDerivedProduct.Storage→FHIR.HashableFHIR.R4.BiologicallyDerivedProduct.Storage→FHIR.JsonFHIR.R4.BiologicallyDerivedProduct.Storage→FHIR.Xml
- Direction
- FHIR.R4.BiologicallyDerivedProduct uses FHIR, so a change to FHIR can break FHIR.R4.BiologicallyDerivedProduct, while a change to FHIR.R4.BiologicallyDerivedProduct can't break FHIR.
- Position
- Below the diagonal: FHIR.R4.BiologicallyDerivedProduct uses a module listed above it, which is the healthy direction.
16→3 FHIR.R4.BiologicallyDerivedProduct uses FHIR.R4✕
- Connections
- 4 pairs of types, where a type in FHIR.R4.BiologicallyDerivedProduct uses a type in FHIR.R4.
- The types involved
FHIR.R4.BiologicallyDerivedProduct.Collection→FHIR.R4.ModelFHIR.R4.BiologicallyDerivedProduct.Manipulation→FHIR.R4.ModelFHIR.R4.BiologicallyDerivedProduct.Processing→FHIR.R4.ModelFHIR.R4.BiologicallyDerivedProduct.Storage→FHIR.R4.Model
- Direction
- FHIR.R4.BiologicallyDerivedProduct uses FHIR.R4, so a change to FHIR.R4 can break FHIR.R4.BiologicallyDerivedProduct, while a change to FHIR.R4.BiologicallyDerivedProduct can't break FHIR.R4.
- Position
- Below the diagonal: FHIR.R4.BiologicallyDerivedProduct uses a module listed above it, which is the healthy direction.
17→1 FHIR.R4.Bundle uses FHIR✕
- Connections
- 6 pairs of types, where a type in FHIR.R4.Bundle uses a type in FHIR.
- The types involved
FHIR.R4.Bundle.Entry→FHIR.HashableFHIR.R4.Bundle.Entry→FHIR.JsonFHIR.R4.Bundle.Entry→FHIR.XmlFHIR.R4.Bundle.Link→FHIR.HashableFHIR.R4.Bundle.Link→FHIR.JsonFHIR.R4.Bundle.Link→FHIR.Xml
- Direction
- FHIR.R4.Bundle uses FHIR, so a change to FHIR can break FHIR.R4.Bundle, while a change to FHIR.R4.Bundle can't break FHIR.
- Position
- Below the diagonal: FHIR.R4.Bundle uses a module listed above it, which is the healthy direction.
17→3 FHIR.R4.Bundle uses FHIR.R4✕
- Connections
- 2 pairs of types, where a type in FHIR.R4.Bundle uses a type in FHIR.R4.
- The types involved
FHIR.R4.Bundle.Entry→FHIR.R4.ModelFHIR.R4.Bundle.Link→FHIR.R4.Model
- Direction
- FHIR.R4.Bundle uses FHIR.R4, so a change to FHIR.R4 can break FHIR.R4.Bundle, while a change to FHIR.R4.Bundle can't break FHIR.R4.
- Position
- Below the diagonal: FHIR.R4.Bundle uses a module listed above it, which is the healthy direction.
18→1 FHIR.R4.Bundle.Entry uses FHIR✕
- Connections
- 9 pairs of types, where a type in FHIR.R4.Bundle.Entry uses a type in FHIR.
- The types involved
FHIR.R4.Bundle.Entry.Request→FHIR.HashableFHIR.R4.Bundle.Entry.Request→FHIR.JsonFHIR.R4.Bundle.Entry.Request→FHIR.XmlFHIR.R4.Bundle.Entry.Response→FHIR.HashableFHIR.R4.Bundle.Entry.Response→FHIR.JsonFHIR.R4.Bundle.Entry.Response→FHIR.XmlFHIR.R4.Bundle.Entry.Search→FHIR.HashableFHIR.R4.Bundle.Entry.Search→FHIR.JsonFHIR.R4.Bundle.Entry.Search→FHIR.Xml
- Direction
- FHIR.R4.Bundle.Entry uses FHIR, so a change to FHIR can break FHIR.R4.Bundle.Entry, while a change to FHIR.R4.Bundle.Entry can't break FHIR.
- Position
- Below the diagonal: FHIR.R4.Bundle.Entry uses a module listed above it, which is the healthy direction.
18→3 FHIR.R4.Bundle.Entry uses FHIR.R4✕
- Connections
- 3 pairs of types, where a type in FHIR.R4.Bundle.Entry uses a type in FHIR.R4.
- The types involved
FHIR.R4.Bundle.Entry.Request→FHIR.R4.ModelFHIR.R4.Bundle.Entry.Response→FHIR.R4.ModelFHIR.R4.Bundle.Entry.Search→FHIR.R4.Model
- Direction
- FHIR.R4.Bundle.Entry uses FHIR.R4, so a change to FHIR.R4 can break FHIR.R4.Bundle.Entry, while a change to FHIR.R4.Bundle.Entry can't break FHIR.R4.
- Position
- Below the diagonal: FHIR.R4.Bundle.Entry uses a module listed above it, which is the healthy direction.
19→1 FHIR.R4.CapabilityStatement uses FHIR✕
- Connections
- 15 pairs of types, where a type in FHIR.R4.CapabilityStatement uses a type in FHIR.
- The types involved
FHIR.R4.CapabilityStatement.Document→FHIR.HashableFHIR.R4.CapabilityStatement.Document→FHIR.JsonFHIR.R4.CapabilityStatement.Document→FHIR.XmlFHIR.R4.CapabilityStatement.Implementation→FHIR.HashableFHIR.R4.CapabilityStatement.Implementation→FHIR.JsonFHIR.R4.CapabilityStatement.Implementation→FHIR.XmlFHIR.R4.CapabilityStatement.Messaging→FHIR.HashableFHIR.R4.CapabilityStatement.Messaging→FHIR.JsonFHIR.R4.CapabilityStatement.Messaging→FHIR.XmlFHIR.R4.CapabilityStatement.Rest→FHIR.HashableFHIR.R4.CapabilityStatement.Rest→FHIR.JsonFHIR.R4.CapabilityStatement.Rest→FHIR.XmlFHIR.R4.CapabilityStatement.Software→FHIR.HashableFHIR.R4.CapabilityStatement.Software→FHIR.JsonFHIR.R4.CapabilityStatement.Software→FHIR.Xml
- Direction
- FHIR.R4.CapabilityStatement uses FHIR, so a change to FHIR can break FHIR.R4.CapabilityStatement, while a change to FHIR.R4.CapabilityStatement can't break FHIR.
- Position
- Below the diagonal: FHIR.R4.CapabilityStatement uses a module listed above it, which is the healthy direction.
19→3 FHIR.R4.CapabilityStatement uses FHIR.R4✕
- Connections
- 5 pairs of types, where a type in FHIR.R4.CapabilityStatement uses a type in FHIR.R4.
- The types involved
FHIR.R4.CapabilityStatement.Document→FHIR.R4.ModelFHIR.R4.CapabilityStatement.Implementation→FHIR.R4.ModelFHIR.R4.CapabilityStatement.Messaging→FHIR.R4.ModelFHIR.R4.CapabilityStatement.Rest→FHIR.R4.ModelFHIR.R4.CapabilityStatement.Software→FHIR.R4.Model
- Direction
- FHIR.R4.CapabilityStatement uses FHIR.R4, so a change to FHIR.R4 can break FHIR.R4.CapabilityStatement, while a change to FHIR.R4.CapabilityStatement can't break FHIR.R4.
- Position
- Below the diagonal: FHIR.R4.CapabilityStatement uses a module listed above it, which is the healthy direction.
20→1 FHIR.R4.CapabilityStatement.Messaging uses FHIR✕
- Connections
- 6 pairs of types, where a type in FHIR.R4.CapabilityStatement.Messaging uses a type in FHIR.
- The types involved
FHIR.R4.CapabilityStatement.Messaging.Endpoint→FHIR.HashableFHIR.R4.CapabilityStatement.Messaging.Endpoint→FHIR.JsonFHIR.R4.CapabilityStatement.Messaging.Endpoint→FHIR.XmlFHIR.R4.CapabilityStatement.Messaging.SupportedMessage→FHIR.HashableFHIR.R4.CapabilityStatement.Messaging.SupportedMessage→FHIR.JsonFHIR.R4.CapabilityStatement.Messaging.SupportedMessage→FHIR.Xml
- Direction
- FHIR.R4.CapabilityStatement.Messaging uses FHIR, so a change to FHIR can break FHIR.R4.CapabilityStatement.Messaging, while a change to FHIR.R4.CapabilityStatement.Messaging can't break FHIR.
- Position
- Below the diagonal: FHIR.R4.CapabilityStatement.Messaging uses a module listed above it, which is the healthy direction.
20→3 FHIR.R4.CapabilityStatement.Messaging uses FHIR.R4✕
- Connections
- 2 pairs of types, where a type in FHIR.R4.CapabilityStatement.Messaging uses a type in FHIR.R4.
- The types involved
FHIR.R4.CapabilityStatement.Messaging.Endpoint→FHIR.R4.ModelFHIR.R4.CapabilityStatement.Messaging.SupportedMessage→FHIR.R4.Model
- Direction
- FHIR.R4.CapabilityStatement.Messaging uses FHIR.R4, so a change to FHIR.R4 can break FHIR.R4.CapabilityStatement.Messaging, while a change to FHIR.R4.CapabilityStatement.Messaging can't break FHIR.R4.
- Position
- Below the diagonal: FHIR.R4.CapabilityStatement.Messaging uses a module listed above it, which is the healthy direction.
21→1 FHIR.R4.CapabilityStatement.Rest uses FHIR✕
- Connections
- 9 pairs of types, where a type in FHIR.R4.CapabilityStatement.Rest uses a type in FHIR.
- The types involved
FHIR.R4.CapabilityStatement.Rest.Interaction→FHIR.HashableFHIR.R4.CapabilityStatement.Rest.Interaction→FHIR.JsonFHIR.R4.CapabilityStatement.Rest.Interaction→FHIR.XmlFHIR.R4.CapabilityStatement.Rest.Resource→FHIR.HashableFHIR.R4.CapabilityStatement.Rest.Resource→FHIR.JsonFHIR.R4.CapabilityStatement.Rest.Resource→FHIR.XmlFHIR.R4.CapabilityStatement.Rest.Security→FHIR.HashableFHIR.R4.CapabilityStatement.Rest.Security→FHIR.JsonFHIR.R4.CapabilityStatement.Rest.Security→FHIR.Xml
- Direction
- FHIR.R4.CapabilityStatement.Rest uses FHIR, so a change to FHIR can break FHIR.R4.CapabilityStatement.Rest, while a change to FHIR.R4.CapabilityStatement.Rest can't break FHIR.
- Position
- Below the diagonal: FHIR.R4.CapabilityStatement.Rest uses a module listed above it, which is the healthy direction.
21→3 FHIR.R4.CapabilityStatement.Rest uses FHIR.R4✕
- Connections
- 3 pairs of types, where a type in FHIR.R4.CapabilityStatement.Rest uses a type in FHIR.R4.
- The types involved
FHIR.R4.CapabilityStatement.Rest.Interaction→FHIR.R4.ModelFHIR.R4.CapabilityStatement.Rest.Resource→FHIR.R4.ModelFHIR.R4.CapabilityStatement.Rest.Security→FHIR.R4.Model
- Direction
- FHIR.R4.CapabilityStatement.Rest uses FHIR.R4, so a change to FHIR.R4 can break FHIR.R4.CapabilityStatement.Rest, while a change to FHIR.R4.CapabilityStatement.Rest can't break FHIR.R4.
- Position
- Below the diagonal: FHIR.R4.CapabilityStatement.Rest uses a module listed above it, which is the healthy direction.
22→1 FHIR.R4.CapabilityStatement.Rest.Resource uses FHIR✕
- Connections
- 9 pairs of types, where a type in FHIR.R4.CapabilityStatement.Rest.Resource uses a type in FHIR.
- The types involved
FHIR.R4.CapabilityStatement.Rest.Resource.Interaction→FHIR.HashableFHIR.R4.CapabilityStatement.Rest.Resource.Interaction→FHIR.JsonFHIR.R4.CapabilityStatement.Rest.Resource.Interaction→FHIR.XmlFHIR.R4.CapabilityStatement.Rest.Resource.Operation→FHIR.HashableFHIR.R4.CapabilityStatement.Rest.Resource.Operation→FHIR.JsonFHIR.R4.CapabilityStatement.Rest.Resource.Operation→FHIR.XmlFHIR.R4.CapabilityStatement.Rest.Resource.SearchParam→FHIR.HashableFHIR.R4.CapabilityStatement.Rest.Resource.SearchParam→FHIR.JsonFHIR.R4.CapabilityStatement.Rest.Resource.SearchParam→FHIR.Xml
- Direction
- FHIR.R4.CapabilityStatement.Rest.Resource uses FHIR, so a change to FHIR can break FHIR.R4.CapabilityStatement.Rest.Resource, while a change to FHIR.R4.CapabilityStatement.Rest.Resource can't break FHIR.
- Position
- Below the diagonal: FHIR.R4.CapabilityStatement.Rest.Resource uses a module listed above it, which is the healthy direction.
22→3 FHIR.R4.CapabilityStatement.Rest.Resource uses FHIR.R4✕
- Connections
- 3 pairs of types, where a type in FHIR.R4.CapabilityStatement.Rest.Resource uses a type in FHIR.R4.
- The types involved
FHIR.R4.CapabilityStatement.Rest.Resource.Interaction→FHIR.R4.ModelFHIR.R4.CapabilityStatement.Rest.Resource.Operation→FHIR.R4.ModelFHIR.R4.CapabilityStatement.Rest.Resource.SearchParam→FHIR.R4.Model
- Direction
- FHIR.R4.CapabilityStatement.Rest.Resource uses FHIR.R4, so a change to FHIR.R4 can break FHIR.R4.CapabilityStatement.Rest.Resource, while a change to FHIR.R4.CapabilityStatement.Rest.Resource can't break FHIR.R4.
- Position
- Below the diagonal: FHIR.R4.CapabilityStatement.Rest.Resource uses a module listed above it, which is the healthy direction.
23→1 FHIR.R4.CarePlan uses FHIR✕
- Connections
- 3 pairs of types, where a type in FHIR.R4.CarePlan uses a type in FHIR.
- The types involved
FHIR.R4.CarePlan.Activity→FHIR.HashableFHIR.R4.CarePlan.Activity→FHIR.JsonFHIR.R4.CarePlan.Activity→FHIR.Xml
- Direction
- FHIR.R4.CarePlan uses FHIR, so a change to FHIR can break FHIR.R4.CarePlan, while a change to FHIR.R4.CarePlan can't break FHIR.
- Position
- Below the diagonal: FHIR.R4.CarePlan uses a module listed above it, which is the healthy direction.
23→3 FHIR.R4.CarePlan uses FHIR.R4✕
- Connections
- 1 pair of types, where a type in FHIR.R4.CarePlan uses a type in FHIR.R4.
- The types involved
FHIR.R4.CarePlan.Activity→FHIR.R4.Model
- Direction
- FHIR.R4.CarePlan uses FHIR.R4, so a change to FHIR.R4 can break FHIR.R4.CarePlan, while a change to FHIR.R4.CarePlan can't break FHIR.R4.
- Position
- Below the diagonal: FHIR.R4.CarePlan uses a module listed above it, which is the healthy direction.
24→1 FHIR.R4.CarePlan.Activity uses FHIR✕
- Connections
- 3 pairs of types, where a type in FHIR.R4.CarePlan.Activity uses a type in FHIR.
- The types involved
FHIR.R4.CarePlan.Activity.Detail→FHIR.HashableFHIR.R4.CarePlan.Activity.Detail→FHIR.JsonFHIR.R4.CarePlan.Activity.Detail→FHIR.Xml
- Direction
- FHIR.R4.CarePlan.Activity uses FHIR, so a change to FHIR can break FHIR.R4.CarePlan.Activity, while a change to FHIR.R4.CarePlan.Activity can't break FHIR.
- Position
- Below the diagonal: FHIR.R4.CarePlan.Activity uses a module listed above it, which is the healthy direction.
24→3 FHIR.R4.CarePlan.Activity uses FHIR.R4✕
- Connections
- 1 pair of types, where a type in FHIR.R4.CarePlan.Activity uses a type in FHIR.R4.
- The types involved
FHIR.R4.CarePlan.Activity.Detail→FHIR.R4.Model
- Direction
- FHIR.R4.CarePlan.Activity uses FHIR.R4, so a change to FHIR.R4 can break FHIR.R4.CarePlan.Activity, while a change to FHIR.R4.CarePlan.Activity can't break FHIR.R4.
- Position
- Below the diagonal: FHIR.R4.CarePlan.Activity uses a module listed above it, which is the healthy direction.
25→1 FHIR.R4.CareTeam uses FHIR✕
- Connections
- 3 pairs of types, where a type in FHIR.R4.CareTeam uses a type in FHIR.
- The types involved
FHIR.R4.CareTeam.Participant→FHIR.HashableFHIR.R4.CareTeam.Participant→FHIR.JsonFHIR.R4.CareTeam.Participant→FHIR.Xml
- Direction
- FHIR.R4.CareTeam uses FHIR, so a change to FHIR can break FHIR.R4.CareTeam, while a change to FHIR.R4.CareTeam can't break FHIR.
- Position
- Below the diagonal: FHIR.R4.CareTeam uses a module listed above it, which is the healthy direction.
25→3 FHIR.R4.CareTeam uses FHIR.R4✕
- Connections
- 1 pair of types, where a type in FHIR.R4.CareTeam uses a type in FHIR.R4.
- The types involved
FHIR.R4.CareTeam.Participant→FHIR.R4.Model
- Direction
- FHIR.R4.CareTeam uses FHIR.R4, so a change to FHIR.R4 can break FHIR.R4.CareTeam, while a change to FHIR.R4.CareTeam can't break FHIR.R4.
- Position
- Below the diagonal: FHIR.R4.CareTeam uses a module listed above it, which is the healthy direction.
26→1 FHIR.R4.CatalogEntry uses FHIR✕
- Connections
- 3 pairs of types, where a type in FHIR.R4.CatalogEntry uses a type in FHIR.
- The types involved
FHIR.R4.CatalogEntry.RelatedEntry→FHIR.HashableFHIR.R4.CatalogEntry.RelatedEntry→FHIR.JsonFHIR.R4.CatalogEntry.RelatedEntry→FHIR.Xml
- Direction
- FHIR.R4.CatalogEntry uses FHIR, so a change to FHIR can break FHIR.R4.CatalogEntry, while a change to FHIR.R4.CatalogEntry can't break FHIR.
- Position
- Below the diagonal: FHIR.R4.CatalogEntry uses a module listed above it, which is the healthy direction.
26→3 FHIR.R4.CatalogEntry uses FHIR.R4✕
- Connections
- 1 pair of types, where a type in FHIR.R4.CatalogEntry uses a type in FHIR.R4.
- The types involved
FHIR.R4.CatalogEntry.RelatedEntry→FHIR.R4.Model
- Direction
- FHIR.R4.CatalogEntry uses FHIR.R4, so a change to FHIR.R4 can break FHIR.R4.CatalogEntry, while a change to FHIR.R4.CatalogEntry can't break FHIR.R4.
- Position
- Below the diagonal: FHIR.R4.CatalogEntry uses a module listed above it, which is the healthy direction.
27→1 FHIR.R4.ChargeItem uses FHIR✕
- Connections
- 3 pairs of types, where a type in FHIR.R4.ChargeItem uses a type in FHIR.
- The types involved
FHIR.R4.ChargeItem.Performer→FHIR.HashableFHIR.R4.ChargeItem.Performer→FHIR.JsonFHIR.R4.ChargeItem.Performer→FHIR.Xml
- Direction
- FHIR.R4.ChargeItem uses FHIR, so a change to FHIR can break FHIR.R4.ChargeItem, while a change to FHIR.R4.ChargeItem can't break FHIR.
- Position
- Below the diagonal: FHIR.R4.ChargeItem uses a module listed above it, which is the healthy direction.
27→3 FHIR.R4.ChargeItem uses FHIR.R4✕
- Connections
- 1 pair of types, where a type in FHIR.R4.ChargeItem uses a type in FHIR.R4.
- The types involved
FHIR.R4.ChargeItem.Performer→FHIR.R4.Model
- Direction
- FHIR.R4.ChargeItem uses FHIR.R4, so a change to FHIR.R4 can break FHIR.R4.ChargeItem, while a change to FHIR.R4.ChargeItem can't break FHIR.R4.
- Position
- Below the diagonal: FHIR.R4.ChargeItem uses a module listed above it, which is the healthy direction.
28→1 FHIR.R4.ChargeItemDefinition uses FHIR✕
- Connections
- 6 pairs of types, where a type in FHIR.R4.ChargeItemDefinition uses a type in FHIR.
- The types involved
FHIR.R4.ChargeItemDefinition.Applicability→FHIR.HashableFHIR.R4.ChargeItemDefinition.Applicability→FHIR.JsonFHIR.R4.ChargeItemDefinition.Applicability→FHIR.XmlFHIR.R4.ChargeItemDefinition.PropertyGroup→FHIR.HashableFHIR.R4.ChargeItemDefinition.PropertyGroup→FHIR.JsonFHIR.R4.ChargeItemDefinition.PropertyGroup→FHIR.Xml
- Direction
- FHIR.R4.ChargeItemDefinition uses FHIR, so a change to FHIR can break FHIR.R4.ChargeItemDefinition, while a change to FHIR.R4.ChargeItemDefinition can't break FHIR.
- Position
- Below the diagonal: FHIR.R4.ChargeItemDefinition uses a module listed above it, which is the healthy direction.
28→3 FHIR.R4.ChargeItemDefinition uses FHIR.R4✕
- Connections
- 2 pairs of types, where a type in FHIR.R4.ChargeItemDefinition uses a type in FHIR.R4.
- The types involved
FHIR.R4.ChargeItemDefinition.Applicability→FHIR.R4.ModelFHIR.R4.ChargeItemDefinition.PropertyGroup→FHIR.R4.Model
- Direction
- FHIR.R4.ChargeItemDefinition uses FHIR.R4, so a change to FHIR.R4 can break FHIR.R4.ChargeItemDefinition, while a change to FHIR.R4.ChargeItemDefinition can't break FHIR.R4.
- Position
- Below the diagonal: FHIR.R4.ChargeItemDefinition uses a module listed above it, which is the healthy direction.
29→1 FHIR.R4.ChargeItemDefinition.PropertyGroup uses FHIR✕
- Connections
- 3 pairs of types, where a type in FHIR.R4.ChargeItemDefinition.PropertyGroup uses a type in FHIR.
- The types involved
FHIR.R4.ChargeItemDefinition.PropertyGroup.PriceComponent→FHIR.HashableFHIR.R4.ChargeItemDefinition.PropertyGroup.PriceComponent→FHIR.JsonFHIR.R4.ChargeItemDefinition.PropertyGroup.PriceComponent→FHIR.Xml
- Direction
- FHIR.R4.ChargeItemDefinition.PropertyGroup uses FHIR, so a change to FHIR can break FHIR.R4.ChargeItemDefinition.PropertyGroup, while a change to FHIR.R4.ChargeItemDefinition.PropertyGroup can't break FHIR.
- Position
- Below the diagonal: FHIR.R4.ChargeItemDefinition.PropertyGroup uses a module listed above it, which is the healthy direction.
29→3 FHIR.R4.ChargeItemDefinition.PropertyGroup uses FHIR.R4✕
- Connections
- 1 pair of types, where a type in FHIR.R4.ChargeItemDefinition.PropertyGroup uses a type in FHIR.R4.
- The types involved
FHIR.R4.ChargeItemDefinition.PropertyGroup.PriceComponent→FHIR.R4.Model
- Direction
- FHIR.R4.ChargeItemDefinition.PropertyGroup uses FHIR.R4, so a change to FHIR.R4 can break FHIR.R4.ChargeItemDefinition.PropertyGroup, while a change to FHIR.R4.ChargeItemDefinition.PropertyGroup can't break FHIR.R4.
- Position
- Below the diagonal: FHIR.R4.ChargeItemDefinition.PropertyGroup uses a module listed above it, which is the healthy direction.
30→1 FHIR.R4.Claim uses FHIR✕
- Connections
- 27 pairs of types, where a type in FHIR.R4.Claim uses a type in FHIR. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
FHIR.R4.Claim.Accident→FHIR.HashableFHIR.R4.Claim.Accident→FHIR.JsonFHIR.R4.Claim.Accident→FHIR.XmlFHIR.R4.Claim.CareTeam→FHIR.HashableFHIR.R4.Claim.CareTeam→FHIR.JsonFHIR.R4.Claim.CareTeam→FHIR.XmlFHIR.R4.Claim.Diagnosis→FHIR.HashableFHIR.R4.Claim.Diagnosis→FHIR.JsonFHIR.R4.Claim.Diagnosis→FHIR.XmlFHIR.R4.Claim.Insurance→FHIR.HashableFHIR.R4.Claim.Insurance→FHIR.JsonFHIR.R4.Claim.Insurance→FHIR.XmlFHIR.R4.Claim.Item→FHIR.HashableFHIR.R4.Claim.Item→FHIR.JsonFHIR.R4.Claim.Item→FHIR.XmlFHIR.R4.Claim.Payee→FHIR.HashableFHIR.R4.Claim.Payee→FHIR.JsonFHIR.R4.Claim.Payee→FHIR.XmlFHIR.R4.Claim.Procedure→FHIR.HashableFHIR.R4.Claim.Procedure→FHIR.JsonFHIR.R4.Claim.Procedure→FHIR.XmlFHIR.R4.Claim.Related→FHIR.HashableFHIR.R4.Claim.Related→FHIR.JsonFHIR.R4.Claim.Related→FHIR.XmlFHIR.R4.Claim.SupportingInfo→FHIR.Hashable
- Direction
- FHIR.R4.Claim uses FHIR, so a change to FHIR can break FHIR.R4.Claim, while a change to FHIR.R4.Claim can't break FHIR.
- Position
- Below the diagonal: FHIR.R4.Claim uses a module listed above it, which is the healthy direction.
30→3 FHIR.R4.Claim uses FHIR.R4✕
- Connections
- 9 pairs of types, where a type in FHIR.R4.Claim uses a type in FHIR.R4.
- The types involved
FHIR.R4.Claim.Accident→FHIR.R4.ModelFHIR.R4.Claim.CareTeam→FHIR.R4.ModelFHIR.R4.Claim.Diagnosis→FHIR.R4.ModelFHIR.R4.Claim.Insurance→FHIR.R4.ModelFHIR.R4.Claim.Item→FHIR.R4.ModelFHIR.R4.Claim.Payee→FHIR.R4.ModelFHIR.R4.Claim.Procedure→FHIR.R4.ModelFHIR.R4.Claim.Related→FHIR.R4.ModelFHIR.R4.Claim.SupportingInfo→FHIR.R4.Model
- Direction
- FHIR.R4.Claim uses FHIR.R4, so a change to FHIR.R4 can break FHIR.R4.Claim, while a change to FHIR.R4.Claim can't break FHIR.R4.
- Position
- Below the diagonal: FHIR.R4.Claim uses a module listed above it, which is the healthy direction.
31→1 FHIR.R4.Claim.Item uses FHIR✕
- Connections
- 3 pairs of types, where a type in FHIR.R4.Claim.Item uses a type in FHIR.
- The types involved
FHIR.R4.Claim.Item.Detail→FHIR.HashableFHIR.R4.Claim.Item.Detail→FHIR.JsonFHIR.R4.Claim.Item.Detail→FHIR.Xml
- Direction
- FHIR.R4.Claim.Item uses FHIR, so a change to FHIR can break FHIR.R4.Claim.Item, while a change to FHIR.R4.Claim.Item can't break FHIR.
- Position
- Below the diagonal: FHIR.R4.Claim.Item uses a module listed above it, which is the healthy direction.
31→3 FHIR.R4.Claim.Item uses FHIR.R4✕
- Connections
- 1 pair of types, where a type in FHIR.R4.Claim.Item uses a type in FHIR.R4.
- The types involved
FHIR.R4.Claim.Item.Detail→FHIR.R4.Model
- Direction
- FHIR.R4.Claim.Item uses FHIR.R4, so a change to FHIR.R4 can break FHIR.R4.Claim.Item, while a change to FHIR.R4.Claim.Item can't break FHIR.R4.
- Position
- Below the diagonal: FHIR.R4.Claim.Item uses a module listed above it, which is the healthy direction.
32→1 FHIR.R4.Claim.Item.Detail uses FHIR✕
- Connections
- 3 pairs of types, where a type in FHIR.R4.Claim.Item.Detail uses a type in FHIR.
- The types involved
FHIR.R4.Claim.Item.Detail.SubDetail→FHIR.HashableFHIR.R4.Claim.Item.Detail.SubDetail→FHIR.JsonFHIR.R4.Claim.Item.Detail.SubDetail→FHIR.Xml
- Direction
- FHIR.R4.Claim.Item.Detail uses FHIR, so a change to FHIR can break FHIR.R4.Claim.Item.Detail, while a change to FHIR.R4.Claim.Item.Detail can't break FHIR.
- Position
- Below the diagonal: FHIR.R4.Claim.Item.Detail uses a module listed above it, which is the healthy direction.
32→3 FHIR.R4.Claim.Item.Detail uses FHIR.R4✕
- Connections
- 1 pair of types, where a type in FHIR.R4.Claim.Item.Detail uses a type in FHIR.R4.
- The types involved
FHIR.R4.Claim.Item.Detail.SubDetail→FHIR.R4.Model
- Direction
- FHIR.R4.Claim.Item.Detail uses FHIR.R4, so a change to FHIR.R4 can break FHIR.R4.Claim.Item.Detail, while a change to FHIR.R4.Claim.Item.Detail can't break FHIR.R4.
- Position
- Below the diagonal: FHIR.R4.Claim.Item.Detail uses a module listed above it, which is the healthy direction.
33→1 FHIR.R4.ClaimResponse uses FHIR✕
- Connections
- 21 pairs of types, where a type in FHIR.R4.ClaimResponse uses a type in FHIR.
- The types involved
FHIR.R4.ClaimResponse.AddItem→FHIR.HashableFHIR.R4.ClaimResponse.AddItem→FHIR.JsonFHIR.R4.ClaimResponse.AddItem→FHIR.XmlFHIR.R4.ClaimResponse.Error→FHIR.HashableFHIR.R4.ClaimResponse.Error→FHIR.JsonFHIR.R4.ClaimResponse.Error→FHIR.XmlFHIR.R4.ClaimResponse.Insurance→FHIR.HashableFHIR.R4.ClaimResponse.Insurance→FHIR.JsonFHIR.R4.ClaimResponse.Insurance→FHIR.XmlFHIR.R4.ClaimResponse.Item→FHIR.HashableFHIR.R4.ClaimResponse.Item→FHIR.JsonFHIR.R4.ClaimResponse.Item→FHIR.XmlFHIR.R4.ClaimResponse.Payment→FHIR.HashableFHIR.R4.ClaimResponse.Payment→FHIR.JsonFHIR.R4.ClaimResponse.Payment→FHIR.XmlFHIR.R4.ClaimResponse.ProcessNote→FHIR.HashableFHIR.R4.ClaimResponse.ProcessNote→FHIR.JsonFHIR.R4.ClaimResponse.ProcessNote→FHIR.XmlFHIR.R4.ClaimResponse.Total→FHIR.HashableFHIR.R4.ClaimResponse.Total→FHIR.JsonFHIR.R4.ClaimResponse.Total→FHIR.Xml
- Direction
- FHIR.R4.ClaimResponse uses FHIR, so a change to FHIR can break FHIR.R4.ClaimResponse, while a change to FHIR.R4.ClaimResponse can't break FHIR.
- Position
- Below the diagonal: FHIR.R4.ClaimResponse uses a module listed above it, which is the healthy direction.
33→3 FHIR.R4.ClaimResponse uses FHIR.R4✕
- Connections
- 7 pairs of types, where a type in FHIR.R4.ClaimResponse uses a type in FHIR.R4.
- The types involved
FHIR.R4.ClaimResponse.AddItem→FHIR.R4.ModelFHIR.R4.ClaimResponse.Error→FHIR.R4.ModelFHIR.R4.ClaimResponse.Insurance→FHIR.R4.ModelFHIR.R4.ClaimResponse.Item→FHIR.R4.ModelFHIR.R4.ClaimResponse.Payment→FHIR.R4.ModelFHIR.R4.ClaimResponse.ProcessNote→FHIR.R4.ModelFHIR.R4.ClaimResponse.Total→FHIR.R4.Model
- Direction
- FHIR.R4.ClaimResponse uses FHIR.R4, so a change to FHIR.R4 can break FHIR.R4.ClaimResponse, while a change to FHIR.R4.ClaimResponse can't break FHIR.R4.
- Position
- Below the diagonal: FHIR.R4.ClaimResponse uses a module listed above it, which is the healthy direction.
34→1 FHIR.R4.ClaimResponse.AddItem uses FHIR✕
- Connections
- 3 pairs of types, where a type in FHIR.R4.ClaimResponse.AddItem uses a type in FHIR.
- The types involved
FHIR.R4.ClaimResponse.AddItem.Detail→FHIR.HashableFHIR.R4.ClaimResponse.AddItem.Detail→FHIR.JsonFHIR.R4.ClaimResponse.AddItem.Detail→FHIR.Xml
- Direction
- FHIR.R4.ClaimResponse.AddItem uses FHIR, so a change to FHIR can break FHIR.R4.ClaimResponse.AddItem, while a change to FHIR.R4.ClaimResponse.AddItem can't break FHIR.
- Position
- Below the diagonal: FHIR.R4.ClaimResponse.AddItem uses a module listed above it, which is the healthy direction.
34→3 FHIR.R4.ClaimResponse.AddItem uses FHIR.R4✕
- Connections
- 1 pair of types, where a type in FHIR.R4.ClaimResponse.AddItem uses a type in FHIR.R4.
- The types involved
FHIR.R4.ClaimResponse.AddItem.Detail→FHIR.R4.Model
- Direction
- FHIR.R4.ClaimResponse.AddItem uses FHIR.R4, so a change to FHIR.R4 can break FHIR.R4.ClaimResponse.AddItem, while a change to FHIR.R4.ClaimResponse.AddItem can't break FHIR.R4.
- Position
- Below the diagonal: FHIR.R4.ClaimResponse.AddItem uses a module listed above it, which is the healthy direction.
35→1 FHIR.R4.ClaimResponse.AddItem.Detail uses FHIR✕
- Connections
- 3 pairs of types, where a type in FHIR.R4.ClaimResponse.AddItem.Detail uses a type in FHIR.
- The types involved
FHIR.R4.ClaimResponse.AddItem.Detail.SubDetail→FHIR.HashableFHIR.R4.ClaimResponse.AddItem.Detail.SubDetail→FHIR.JsonFHIR.R4.ClaimResponse.AddItem.Detail.SubDetail→FHIR.Xml
- Direction
- FHIR.R4.ClaimResponse.AddItem.Detail uses FHIR, so a change to FHIR can break FHIR.R4.ClaimResponse.AddItem.Detail, while a change to FHIR.R4.ClaimResponse.AddItem.Detail can't break FHIR.
- Position
- Below the diagonal: FHIR.R4.ClaimResponse.AddItem.Detail uses a module listed above it, which is the healthy direction.
35→3 FHIR.R4.ClaimResponse.AddItem.Detail uses FHIR.R4✕
- Connections
- 1 pair of types, where a type in FHIR.R4.ClaimResponse.AddItem.Detail uses a type in FHIR.R4.
- The types involved
FHIR.R4.ClaimResponse.AddItem.Detail.SubDetail→FHIR.R4.Model
- Direction
- FHIR.R4.ClaimResponse.AddItem.Detail uses FHIR.R4, so a change to FHIR.R4 can break FHIR.R4.ClaimResponse.AddItem.Detail, while a change to FHIR.R4.ClaimResponse.AddItem.Detail can't break FHIR.R4.
- Position
- Below the diagonal: FHIR.R4.ClaimResponse.AddItem.Detail uses a module listed above it, which is the healthy direction.
36→1 FHIR.R4.ClaimResponse.Item uses FHIR✕
- Connections
- 6 pairs of types, where a type in FHIR.R4.ClaimResponse.Item uses a type in FHIR.
- The types involved
FHIR.R4.ClaimResponse.Item.Adjudication→FHIR.HashableFHIR.R4.ClaimResponse.Item.Adjudication→FHIR.JsonFHIR.R4.ClaimResponse.Item.Adjudication→FHIR.XmlFHIR.R4.ClaimResponse.Item.Detail→FHIR.HashableFHIR.R4.ClaimResponse.Item.Detail→FHIR.JsonFHIR.R4.ClaimResponse.Item.Detail→FHIR.Xml
- Direction
- FHIR.R4.ClaimResponse.Item uses FHIR, so a change to FHIR can break FHIR.R4.ClaimResponse.Item, while a change to FHIR.R4.ClaimResponse.Item can't break FHIR.
- Position
- Below the diagonal: FHIR.R4.ClaimResponse.Item uses a module listed above it, which is the healthy direction.
36→3 FHIR.R4.ClaimResponse.Item uses FHIR.R4✕
- Connections
- 2 pairs of types, where a type in FHIR.R4.ClaimResponse.Item uses a type in FHIR.R4.
- The types involved
FHIR.R4.ClaimResponse.Item.Adjudication→FHIR.R4.ModelFHIR.R4.ClaimResponse.Item.Detail→FHIR.R4.Model
- Direction
- FHIR.R4.ClaimResponse.Item uses FHIR.R4, so a change to FHIR.R4 can break FHIR.R4.ClaimResponse.Item, while a change to FHIR.R4.ClaimResponse.Item can't break FHIR.R4.
- Position
- Below the diagonal: FHIR.R4.ClaimResponse.Item uses a module listed above it, which is the healthy direction.
37→1 FHIR.R4.ClaimResponse.Item.Detail uses FHIR✕
- Connections
- 3 pairs of types, where a type in FHIR.R4.ClaimResponse.Item.Detail uses a type in FHIR.
- The types involved
FHIR.R4.ClaimResponse.Item.Detail.SubDetail→FHIR.HashableFHIR.R4.ClaimResponse.Item.Detail.SubDetail→FHIR.JsonFHIR.R4.ClaimResponse.Item.Detail.SubDetail→FHIR.Xml
- Direction
- FHIR.R4.ClaimResponse.Item.Detail uses FHIR, so a change to FHIR can break FHIR.R4.ClaimResponse.Item.Detail, while a change to FHIR.R4.ClaimResponse.Item.Detail can't break FHIR.
- Position
- Below the diagonal: FHIR.R4.ClaimResponse.Item.Detail uses a module listed above it, which is the healthy direction.
37→3 FHIR.R4.ClaimResponse.Item.Detail uses FHIR.R4✕
- Connections
- 1 pair of types, where a type in FHIR.R4.ClaimResponse.Item.Detail uses a type in FHIR.R4.
- The types involved
FHIR.R4.ClaimResponse.Item.Detail.SubDetail→FHIR.R4.Model
- Direction
- FHIR.R4.ClaimResponse.Item.Detail uses FHIR.R4, so a change to FHIR.R4 can break FHIR.R4.ClaimResponse.Item.Detail, while a change to FHIR.R4.ClaimResponse.Item.Detail can't break FHIR.R4.
- Position
- Below the diagonal: FHIR.R4.ClaimResponse.Item.Detail uses a module listed above it, which is the healthy direction.
38→1 FHIR.R4.ClinicalImpression uses FHIR✕
- Connections
- 6 pairs of types, where a type in FHIR.R4.ClinicalImpression uses a type in FHIR.
- The types involved
FHIR.R4.ClinicalImpression.Finding→FHIR.HashableFHIR.R4.ClinicalImpression.Finding→FHIR.JsonFHIR.R4.ClinicalImpression.Finding→FHIR.XmlFHIR.R4.ClinicalImpression.Investigation→FHIR.HashableFHIR.R4.ClinicalImpression.Investigation→FHIR.JsonFHIR.R4.ClinicalImpression.Investigation→FHIR.Xml
- Direction
- FHIR.R4.ClinicalImpression uses FHIR, so a change to FHIR can break FHIR.R4.ClinicalImpression, while a change to FHIR.R4.ClinicalImpression can't break FHIR.
- Position
- Below the diagonal: FHIR.R4.ClinicalImpression uses a module listed above it, which is the healthy direction.
38→3 FHIR.R4.ClinicalImpression uses FHIR.R4✕
- Connections
- 2 pairs of types, where a type in FHIR.R4.ClinicalImpression uses a type in FHIR.R4.
- The types involved
FHIR.R4.ClinicalImpression.Finding→FHIR.R4.ModelFHIR.R4.ClinicalImpression.Investigation→FHIR.R4.Model
- Direction
- FHIR.R4.ClinicalImpression uses FHIR.R4, so a change to FHIR.R4 can break FHIR.R4.ClinicalImpression, while a change to FHIR.R4.ClinicalImpression can't break FHIR.R4.
- Position
- Below the diagonal: FHIR.R4.ClinicalImpression uses a module listed above it, which is the healthy direction.
39→1 FHIR.R4.CodeSystem uses FHIR✕
- Connections
- 9 pairs of types, where a type in FHIR.R4.CodeSystem uses a type in FHIR.
- The types involved
FHIR.R4.CodeSystem.Concept→FHIR.HashableFHIR.R4.CodeSystem.Concept→FHIR.JsonFHIR.R4.CodeSystem.Concept→FHIR.XmlFHIR.R4.CodeSystem.Filter→FHIR.HashableFHIR.R4.CodeSystem.Filter→FHIR.JsonFHIR.R4.CodeSystem.Filter→FHIR.XmlFHIR.R4.CodeSystem.Property→FHIR.HashableFHIR.R4.CodeSystem.Property→FHIR.JsonFHIR.R4.CodeSystem.Property→FHIR.Xml
- Direction
- FHIR.R4.CodeSystem uses FHIR, so a change to FHIR can break FHIR.R4.CodeSystem, while a change to FHIR.R4.CodeSystem can't break FHIR.
- Position
- Below the diagonal: FHIR.R4.CodeSystem uses a module listed above it, which is the healthy direction.
39→3 FHIR.R4.CodeSystem uses FHIR.R4✕
- Connections
- 3 pairs of types, where a type in FHIR.R4.CodeSystem uses a type in FHIR.R4.
- The types involved
FHIR.R4.CodeSystem.Concept→FHIR.R4.ModelFHIR.R4.CodeSystem.Filter→FHIR.R4.ModelFHIR.R4.CodeSystem.Property→FHIR.R4.Model
- Direction
- FHIR.R4.CodeSystem uses FHIR.R4, so a change to FHIR.R4 can break FHIR.R4.CodeSystem, while a change to FHIR.R4.CodeSystem can't break FHIR.R4.
- Position
- Below the diagonal: FHIR.R4.CodeSystem uses a module listed above it, which is the healthy direction.
40→1 FHIR.R4.CodeSystem.Concept uses FHIR✕
- Connections
- 6 pairs of types, where a type in FHIR.R4.CodeSystem.Concept uses a type in FHIR.
- The types involved
FHIR.R4.CodeSystem.Concept.Designation→FHIR.HashableFHIR.R4.CodeSystem.Concept.Designation→FHIR.JsonFHIR.R4.CodeSystem.Concept.Designation→FHIR.XmlFHIR.R4.CodeSystem.Concept.Property→FHIR.HashableFHIR.R4.CodeSystem.Concept.Property→FHIR.JsonFHIR.R4.CodeSystem.Concept.Property→FHIR.Xml
- Direction
- FHIR.R4.CodeSystem.Concept uses FHIR, so a change to FHIR can break FHIR.R4.CodeSystem.Concept, while a change to FHIR.R4.CodeSystem.Concept can't break FHIR.
- Position
- Below the diagonal: FHIR.R4.CodeSystem.Concept uses a module listed above it, which is the healthy direction.
40→3 FHIR.R4.CodeSystem.Concept uses FHIR.R4✕
- Connections
- 2 pairs of types, where a type in FHIR.R4.CodeSystem.Concept uses a type in FHIR.R4.
- The types involved
FHIR.R4.CodeSystem.Concept.Designation→FHIR.R4.ModelFHIR.R4.CodeSystem.Concept.Property→FHIR.R4.Model
- Direction
- FHIR.R4.CodeSystem.Concept uses FHIR.R4, so a change to FHIR.R4 can break FHIR.R4.CodeSystem.Concept, while a change to FHIR.R4.CodeSystem.Concept can't break FHIR.R4.
- Position
- Below the diagonal: FHIR.R4.CodeSystem.Concept uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 12 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 3 | High / Critical |
| A07:2025 — Authentication Failures | 2 | High / Critical |
Roadmap
Top priorities: Resolve the 13 Orphaned file finding(s) in Knowledge Freshness — start with common_structure_definition.rb, REDACTED, REDACTED; Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them; Resolve the 1 Orphaned knowledge finding(s) in Knowledge Freshness — start with evaluate.rb.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 13 Orphaned file finding(s) in Knowledge Freshness — start with common_structure_definition.rb, REDACTED, REDACTED. | +10.4 pts | Medium | Knowledge Freshness |
| Resolve the 1 Orphaned knowledge finding(s) in Knowledge Freshness — start with evaluate.rb. | +4.7 pts | Low | Knowledge Freshness |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +8.6 pts | Medium | Architecture documentation |
| Add a SAST step to CI running what this repository's stack ships: brakeman for Rails apps, otherwise `semgrep --config=auto` or CodeQL's ruby pack — so a security regression fails the build instead of landing. | +3.5 pts | Medium | Security & performance tooling |
| Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite. | +3.2 pts | Medium | Documentation (README) |
| Resolve the 1 Further orphaned files (smaller) finding(s) in Knowledge Freshness. | +1.6 pts | Low | Knowledge Freshness |
| Adopt a checker and raise it file by file: with Sorbet, `srb init` (or `bundle exec tapioca init`) commits `sorbet/config`, then move each file's sigil from `# typed: false` to `# typed: true` and on to `strict` as its methods get `sig`s — `spoom bump` does the moving; with Steep, write RBS signatures and `check` the product directories in the `Steepfile` under `D::Ruby.default` or `strict`, not `lenient`. Then pay down the assertions rather than adding to them: each `T.must` is a nil the checker could not rule out — narrow it (`return unless x`, `x&.`, `if (y = x)`), make the attribute non-nilable and set it in `initialize`, or change the method so the nil cannot arrive. | +3.1 pts | Medium | Nullable reference types |
| Swallowed exception (caught, then discarded) | +2.1 pts | Medium | Exception handling |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.0 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 5.1 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 5.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| lib/fhir_models/fhir_ext/common_structure_definition.rb | 6.0 | Mixed | Explicit Debt: TodoComment |
| lib/fhir_models/generator/template.rb | 6.0 | Mixed | Explicit Debt: TodoComment |
| lib/fhir_models/bootstrap/hashable.rb | 6.0 | Mixed | Explicit Debt: TodoComment |
| lib/fhir_models/fhirpath/evaluate.rb | 7.1 | Mixed | Cyclomatic Complexity: FHIRPath.compute (cyclomatic 143) |
| REDACTED | 7.2 | Mixed | Secrets (history): REDACTED: REDACTED |
| lib/fhir_models/bootstrap/xml.rb | 7.4 | Mixed | Cyclomatic Complexity: InstanceXml.hash_to_xml_node (cyclomatic 17) |
| lib/fhir_models/generator/class_generator.rb | 7.8 | Mixed | Cyclomatic Complexity: ClassGenerator.generate_class (cyclomatic 35) |
| REDACTED | 7.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 7.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| lib/fhir_models/fhir.rb | 8.2 | Near-clean | Explicit Debt: TodoComment |
| lib/fhir_models/fhirpath/expression.rb | 8.2 | Near-clean | Explicit Debt: TodoComment |
| lib/fhir_models/generator/ig_loader.rb | 8.5 | Near-clean | Cyclomatic Complexity: IGLoader.load_ig (cyclomatic 18) |
| lib/fhir_models/generator/ig_resources.rb | 8.5 | Near-clean | Cognitive Complexity: IGResources.get_codes (cognitive 23) |
| lib/fhir_models/r4.rb | 8.5 | Near-clean | Code Duplication: Duplicated block (28 lines × 3) |
| lib/fhir_models/bootstrap/json.rb | 8.5 | Near-clean | Change Coupling: Change coupling: json.rb ↔ xml.rb |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 39 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
What we checked — 39 dimensions across the health lenses
- Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 90 of 102 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: the Ruby half could not be measured — the Ruby suite ran, but the analyzer could not read its coverage for 1 of its 2 unit(s), so a figure over the rest would be a part of the suite. Coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo — a coverage step in CI (SimpleCov, started in .simplecov) shows coverage is measured in your own CI.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. All 14 significant source file(s) were last meaningfully changed so long ago that no living knowledge remains — nothing since has been substantial enough to re-establish ownership (a broad, mechanical sweep that touches many files shallowly does not count, and neither does no activity at all). There is no concentration to measure, so the bus factor is not scored. This is not a clean bill: nobody currently holds working knowledge of this code (see D34 Knowledge Freshness). Counted over 14 of the 43 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated per language (docs/plans/deterministic-engine.md, P5; C# and each NeutralApiArms arm pass): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D26 Project Cohesion — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `(repository root)` (78833 LoC, 3470 module-visible types across 20 directories) is over its size bounds, and whether one unit is a coherent whole or a grab-bag is read from its type references: the parts of it that reach the rest only through its shared core. Those are read over the C#/VB code model, which this unit's source did not supply. Its size alone is no verdict on its cohesion, so none is published.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
13 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was FHIRPath.compute at 143. A further 1 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being FHIR.primitive? at 22 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: lib/fhir_models/fhir.rb (FHIR.primitive? at 22). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
What to do
- Bring the 2 bodies over 60 down to 60 or less in Cyclomatic Complexity — start with FHIRPath.compute (cyclomatic 143), CommonStructureDefinitionCompare.compare_element_definitions (cyclomatic 65). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cyclomatic Complexity from 6.6 to about 7.5/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
D2 · Cognitive Complexity
17 method(s) exceeded the cognitive complexity threshold of 15; the worst was FHIRPath.compute at 321.
What to do
- Bring the 1 body over 120 down to 120 or less in Cognitive Complexity — start with FHIRPath.compute (cognitive 321). — Refactoring it lifts Cognitive Complexity from 4.9 to about 6.1/10.
D3 · God Classes
1 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 1 FileTooLong finding(s) in God Classes — start with evaluate.rb. — One of this dimension's main actionable groups (1 warning-level).
D4 · Code Duplication
1 duplicated block group(s) detected. 0.1 % of the production lines (66 of 78,833) are in a reported copy.
What to do
- Resolve the 1 Duplicated block (28 lines × 3) finding(s) in Code Duplication — start with r4.rb. — One of this dimension's main actionable groups (1 warning-level).
D6 · Cohesion (LCOM4)
0 of 11 classes have LCOM4 above 3.
D11 · Test Reliability
0 flaky across 1 measured tier(s). Ruby (RSpec: repository root, 6 spec files; minitest: repository root, 25 test files): measured (0 flaky).
D12 · Dependency Hygiene
4 outdated direct gem(s), 0 pinning defect(s). 20 declaration(s) graded against rubygems.org, 17 of them against a version resolved in a committed REDACTED. 2 declaration(s) carry a requirement that EXCLUDES the current release; that is a deliberate constraint (a supported-version ceiling or a held-back CI pin) and is counted, not charged. Whether any of these gems is DEPRECATED or YANKED is not graded — rubygems.org publishes no deprecation marker, and a yank removes a version rather than flagging it. Whether any is UNMAINTAINED is not graded either: no registry publishes a maintenance status, and release age does not stand in for one. Whether any is UNUSED is a source question, not a registry one. Known CVEs in this dependency graph are D30's question, read from the manifest there.
D13 · REDACTED Scanning
REDACTED scan ran and found no leaked secrets.
D14 · License Compliance
0 of 10 shipped gem(s) use a banned license. Licences were resolved from rubygems.org over the 10 gem(s) a consumer installs — this repository's runtime declarations closed transitively over its committed REDACTED. Development-group and `add_development_dependency` gems are excluded: they are not distributed with this repository. 1 of them publish no licence on rubygems.org; that is missing data, not a violation, and none of them is charged. This repository publishes itself under Apache-2.0, which is its own choice and is not judged here.
D15 · Churn × Complexity Hotspots
Top hotspots: lib/fhir_models/generator/class_generator.rb (2×35=70)
What to do
- Resolve the 1 Hotspot finding(s) in Churn × Complexity Hotspots — start with class_generator.rb. — One of this dimension's main actionable groups (1 warning-level).
D17 · Explicit Debt
8 deducted task-comment markers across 78833 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 8 TodoComment finding(s) in Explicit Debt — start with hashable.rb (4), fhir.rb, template.rb. — One of this dimension's main actionable groups (8 warning-level).
D28 · Secrets (history)
1 finding(s): 0 critical, 1 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
What to do
- Resolve the 1 REDACTED finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
12 finding(s): 0 critical, 2 high, 10 medium, 0 low. 2 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens.
What to do
- Resolve the 9 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (5), REDACTED, REDACTED. — One of this dimension's main actionable groups (9 warning-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- No action in Static Analysis (SAST) — all 2 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (2 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
3 finding(s): 0 critical, 2 high, 0 medium, 1 low.
What to do
- Resolve the 2 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 1 Low CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
D34 · Knowledge Freshness
14 of 14 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is lib/fhir_models/fhirpath/evaluate.rb. Counted over 14 of the 43 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 13 Orphaned file finding(s) in Knowledge Freshness — start with common_structure_definition.rb, REDACTED, REDACTED. — One of this dimension's main actionable groups (13 recommendation-level).
- Resolve the 1 Orphaned knowledge finding(s) in Knowledge Freshness — start with evaluate.rb. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Further orphaned files (smaller) finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
Strongest change-coupling: json.rb↔xml.rb 71%
What to do
- Resolve the 1 Change coupling finding(s) in Change Coupling — start with json.rb. — One of this dimension's main actionable groups (1 warning-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 2 platform declaration(s) and 20 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
P1 · CI/CD gates
- A CI pipeline exists but no build step was matched — changes may merge without the build ever running. A build step may be invoked directly as a command, or declared as a task that a runner named in the pipeline resolves.
What to do
- Add an explicit build step to your CI pipeline — your stack's own build command, or, if the pipeline delegates to a task runner, a build task that runner executes in CI — so every change is built before merge.
P10 · Library API & versioning
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add brakeman for Rails apps, otherwise `semgrep --config=auto` or CodeQL's ruby pack as a CI step. What was searched, so you can tell an absence from a miss: the 1 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:6
- `test/fixtures/us_core/package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — test/fixtures/us_core/package.json:10
What to do
- Add a SAST step to CI running what this repository's stack ships: brakeman for Rails apps, otherwise `semgrep --config=auto` or CodeQL's ruby pack — so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
X12 · Unreachable branch
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
- `compute` is public and takes `tree` — which it walks as a `Hash` — from its caller, and it calls itself at line 118 (`self.compute`) with a piece of `tree` (and at line 132, line 138, line 158, line 163, line 260, line 306, line 332, line 352, line 365, line 412, line 413, line 443, line 444, line 474, line 475, line 515, line 516, line 549, line 550, line 580) — and nowhere in `compute` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends stack per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. A walk like this one raises `SystemStackError` past about 3,800 levels on the main thread and about 1,000 on a `Thread` — where Puma serves requests and Sidekiq runs jobs (MRI 3.3 and 4.0). `JSON.parse` stops at 100 levels by default, but the other parsers a caller may use do not: `YAML.safe_load` builds 1,400 levels from 2.8 KB, `Oj.load` 100,000, REXML 200,000, and `JSON.load` on json 2.7 (Ruby 3.3's default) or `JSON.parse(…, max_nesting: false)` 58,000. `SystemStackError` is not a `StandardError`: a bare `rescue` or `rescue => e` around the call does not stop it. Thread a depth argument through `compute` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — lib/fhir_models/fhirpath/evaluate.rb:118
- `from_hash` is public, takes a document from its caller (line 48) and hands it to `prune`, which walks `thing` as a `Hash` and calls itself at line 33 (`self.prune`) with a piece of `thing` (and at line 40) — and nowhere in `prune` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends stack per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. A walk like this one raises `SystemStackError` past about 3,800 levels on the main thread and about 1,000 on a `Thread` — where Puma serves requests and Sidekiq runs jobs (MRI 3.3 and 4.0). `JSON.parse` stops at 100 levels by default, but the other parsers a caller may use do not: `YAML.safe_load` builds 1,400 levels from 2.8 KB, `Oj.load` 100,000, REXML 200,000, and `JSON.load` on json 2.7 (Ruby 3.3's default) or `JSON.parse(…, max_nesting: false)` 58,000. `SystemStackError` is not a `StandardError`: a bare `rescue` or `rescue => e` around the call does not stop it. Thread a depth argument through `prune` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — lib/fhir_models/bootstrap/hashable.rb:33
- `remove_fhir_comments` is public and takes `hash` — which it walks as a `Hash` — from its caller, and it calls itself at line 98 (`self.remove_fhir_comments`) with a piece of `hash` (and at line 101) — and nowhere in `remove_fhir_comments` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends stack per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. A walk like this one raises `SystemStackError` past about 3,800 levels on the main thread and about 1,000 on a `Thread` — where Puma serves requests and Sidekiq runs jobs (MRI 3.3 and 4.0). `JSON.parse` stops at 100 levels by default, but the other parsers a caller may use do not: `YAML.safe_load` builds 1,400 levels from 2.8 KB, `Oj.load` 100,000, REXML 200,000, and `JSON.load` on json 2.7 (Ruby 3.3's default) or `JSON.parse(…, max_nesting: false)` 58,000. `SystemStackError` is not a `StandardError`: a bare `rescue` or `rescue => e` around the call does not stop it. Thread a depth argument through `remove_fhir_comments` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — REDACTED:98
- `xml_node_to_hash` is public and takes `node` — which it walks as an XML element — from its caller, and it calls itself at line 34 (`self.xml_node_to_hash`) with a piece of `node` — and nowhere in `xml_node_to_hash` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends stack per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. A walk like this one raises `SystemStackError` past about 3,800 levels on the main thread and about 1,000 on a `Thread` — where Puma serves requests and Sidekiq runs jobs (MRI 3.3 and 4.0). `JSON.parse` stops at 100 levels by default, but the other parsers a caller may use do not: `YAML.safe_load` builds 1,400 levels from 2.8 KB, `Oj.load` 100,000, REXML 200,000, and `JSON.load` on json 2.7 (Ruby 3.3's default) or `JSON.parse(…, max_nesting: false)` 58,000. `SystemStackError` is not a `StandardError`: a bare `rescue` or `rescue => e` around the call does not stop it. Thread a depth argument through `xml_node_to_hash` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — lib/fhir_models/bootstrap/xml.rb:34
- `hash_to_xml_node` is public and takes `hash` — which it walks as a `Hash` — from its caller, and it calls itself at line 110 (`self.hash_to_xml_node`) with a piece of `hash` (and at line 114) — and nowhere in `hash_to_xml_node` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends stack per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. A walk like this one raises `SystemStackError` past about 3,800 levels on the main thread and about 1,000 on a `Thread` — where Puma serves requests and Sidekiq runs jobs (MRI 3.3 and 4.0). `JSON.parse` stops at 100 levels by default, but the other parsers a caller may use do not: `YAML.safe_load` builds 1,400 levels from 2.8 KB, `Oj.load` 100,000, REXML 200,000, and `JSON.load` on json 2.7 (Ruby 3.3's default) or `JSON.parse(…, max_nesting: false)` 58,000. `SystemStackError` is not a `StandardError`: a bare `rescue` or `rescue => e` around the call does not stop it. Thread a depth argument through `hash_to_xml_node` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — lib/fhir_models/bootstrap/xml.rb:110
What to do
- Each finding names the externally-callable member that accepts the document and the self-call that descends, and states that no depth parameter or counter exists anywhere in the walk. Confirm from the two, then thread a depth argument through the walk and reject documents past a fixed maximum, or rewrite it with an explicit stack.
X18 · Disposal-pattern correctness
X21 · Side-effecting pattern guard
X23 · Unguarded diagnostic materialisation
X3 · Exception handling
- `rescue StandardError` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×4) — lib/fhir_models/fhir.rb:46, lib/fhir_models/fhirpath/expression.rb:20, lib/fhir_models/bootstrap/hashable.rb:68, …
- `… rescue previous_node` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — lib/fhir_models/fhirpath/evaluate.rb:293
- `… rescue false` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×3) — lib/fhir_models/fhirpath/evaluate.rb:307, lib/fhir_models/fhirpath/evaluate.rb:353, lib/fhir_models/fhirpath/evaluate.rb:374
- `… rescue 0` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — lib/fhir_models/fhirpath/evaluate.rb:383
What to do
- Swallowed exception (caught, then discarded)
X30 · Support guard that admits what it rejects
X5 · Nullable reference types
- This repository commits no Sorbet configuration (`sorbet/config`) and no `Steepfile`, so nothing type-checks its 624 Ruby product file(s): a nilable value reaches a method call silently and raises `NoMethodError: undefined method … for nil` the first time it is nil. A `# typed:` sigil does nothing without a `sorbet/config` beside the code; a Steep run configured only on a command line is not something this check can read.
What to do
- Adopt a checker and raise it file by file: with Sorbet, `srb init` (or `bundle exec tapioca init`) commits `sorbet/config`, then move each file's sigil from `# typed: false` to `# typed: true` and on to `strict` as its methods get `sig`s — `spoom bump` does the moving; with Steep, write RBS signatures and `check` the product directories in the `Steepfile` under `D::Ruby.default` or `strict`, not `lenient`. Then pay down the assertions rather than adding to them: each `T.must` is a nil the checker could not rule out — narrow it (`return unless x`, `x&.`, `if (y = x)`), make the attribute non-nilable and set it in `initialize`, or change the method so the nil cannot arrive.
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 55.3 | Adequate — gated by X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 99.8 | Exemplary | Strongest area. |
| Maturity | 42.6 | Weak — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 56.8 | Adequate — gated by P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 83.2 | Strong | Solid. |
Unscored — 2 check(s) recorded observations but carry no score
- D36 Supply-chain Provenance & Signing — 1 observation(s) recorded · The CI pipeline publishes no artifact — no package publish, container push or release with files to download. Supply-chain provenance, signing and an SBOM describe a PUBLISHED artifact for the people who obtain it, so there is nothing to attest here; a deployment of the service itself publishes nothing for anyone else to verify. Add them to the release pipeline when this repo starts publishing artifacts (a package, a container image, or a release with downloadable files). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
- X10 Duplicated predicate — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 2 control(s) we could not find positive evidence for
- P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 75 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: this repository's Ruby imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No class in this Ruby code is a Rails controller, a Sinatra, Grape or Roda app, a Hanami action or a Rack app (an instance `call(env)`), so no request handler shares state between request threads.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — no class or module declares an abstract method
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in an ActiveRecord or Sequel migration, a db/schema.rb table or a Mongoid document — and no database or data-store client (an ActiveRecord model, Sequel, pg, mysql2, sqlite3, Mongo, …) in the source either, so this repository keeps no data at rest for these controls to protect.
- C2 Access Controls — No access-control surface detected in the analyzed source — this repository draws no route and defines no request handler (no Rails routes.draw or controller, no Sinatra, Roda or Grape application, no Hanami action). Access control is therefore N/A here — a gem is authorized by the application that mounts it, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named column (email, first_name, date_of_birth, phone_number, …) or stored credential in an ActiveRecord or Sequel migration, db/schema.rb or a Mongoid document — and no database client (an ActiveRecord model, Sequel, pg, mysql2, Mongo) in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a hosted backend configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in an ActiveRecord or Sequel migration, db/schema.rb or a Mongoid document — and no database client (ActiveRecord, Sequel, pg, mysql2, mongo, …) in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in an ActiveRecord or Sequel migration, a db/schema.rb table or a Mongoid document — and no database or data-store client (an ActiveRecord model, Sequel, pg, mysql2, sqlite3, Mongo, …) in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D10 Test Quality — ~3140 lines of test source are present (.rb) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D16 Bus Factor — dormant codebase — no living knowledge left to concentrate
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D19 Documentation Quality — No runnable or published unit to look for an example in, and no multi-project root README to look for a map in; the other documentation kinds are withheld (see the gaps), so documentation quality is not applicable here.
- D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
- D21 Naming Consistency — N/A — too few peers to establish a naming convention (3002 declarations, no unit with a dominant convention).
- D22 Internal API Consistency — API consistency is measured on C#, TypeScript, Go only; the exposed Ruby surface was not measured.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .rb, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D26 Project Cohesion — D26 could not read how the parts of this repository's one build unit reference each other, so its cohesion was not measured. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D27 Navigability — symbol resolution incomplete — navigability not assessed
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D5 Coupling — Not applicable — this RubyGems build ships 1 production module(s), so there is no coupling BETWEEN modules to measure. (Its test and non-production modules are not part of the shipped graph.)
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not measured — Ruby suite
- DM1 Domain Modelling — not scored — this repository shows none of the 3 signals this lens looks for
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- M4 Documentation accuracy — Not applicable: the 6 current-state document(s) make no claim of a kind M4 checks.
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P2 Observability — This repository's Ruby source (1 module(s), 631 file(s) read) declares no entry point and bootstraps no server, and nothing here deploys a service — it is a library, run inside whatever hosts it, so production observability (structured logging, tracing/metrics, health checks) is N/A. If it grows a binary or a service, the dimension reactivates.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the Ruby source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `x.report(…)` entries in a `Benchmark.ips`/`bm`/`bmbm`/`benchmark`/`memory` block, `benchmark:` entries in a benchmark-driver YAML under a bench* directory, rspec-benchmark `perform_*` expectations where the gem is installed, or benchmark-ips, benchmark-memory, rspec-benchmark or benchmark-driver in a Gemfile or gemspec, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- PF3 Async & latency hygiene — Not applicable: Ruby has no async/await function colour, so there is no asynchronous code for a blocking call to stall.
- S1 Web-Security Posture — No web surface: 624 Ruby file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled TLS certificate validation and obsolete TLS versions, and none was found. This repository serves no HTTP of its own — no `config.ru`, no web framework, Rack or server gem among its gemspec run-time dependencies or its Gemfile's production gems, and no Rails, Rack, Sinatra, Grape, Hanami, WEBrick, Puma or Falcon server defined or booted in its production source — so HTTPS enforcement, HSTS, cookie flags and input validation are N/A here, as they are for a C# library or worker. If this codebase starts serving HTTP, the dimension reactivates automatically.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X1 Async correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X2 Cancellation propagation — no C# was loaded; this repository's Ruby was read, and no request in it can be cancelled by a caller — a Ruby request takes no token: Net::HTTP, Faraday and async-http are stopped from outside the call (Async::Task#stop, Thread#raise, Timeout), not through a parameter
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X27 Collection changed while being enumerated — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Ruby was read, and it logs through none: the standard library's Logger, which Rails.logger is, takes one finished message and no template arguments or fields (as log4net does in C#), so an interpolated message there loses nothing the API could have kept. The console gem (`Console.info`), SemanticLogger, Ougai and dry-logger would be judged.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 6 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Orphaned knowledge lib/fhir_models/fhirpath/evaluate.rb:1
Serious — 67 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Swallowed exception (caught, then discarded) lib/fhir_models/fhir.rb:46
- Swallowed exception (caught, then discarded) lib/fhir_models/fhirpath/evaluate.rb:293
- Swallowed exception (caught, then discarded) lib/fhir_models/fhirpath/evaluate.rb:307
- Swallowed exception (caught, then discarded) lib/fhir_models/fhirpath/evaluate.rb:353
- Swallowed exception (caught, then discarded) lib/fhir_models/fhirpath/evaluate.rb:374
- Swallowed exception (caught, then discarded) lib/fhir_models/fhirpath/evaluate.rb:383
- Swallowed exception (caught, then discarded) lib/fhir_models/fhirpath/expression.rb:20
- Swallowed exception (caught, then discarded) lib/fhir_models/bootstrap/hashable.rb:68
- Swallowed exception (caught, then discarded) REDACTED:145
- TodoComment lib/fhir_models/fhir.rb:31
- TodoComment lib/fhir_models/generator/template.rb:51
- TodoComment lib/fhir_models/fhirpath/expression.rb:21
- TodoComment lib/fhir_models/fhir_ext/common_structure_definition.rb:186
- TodoComment lib/fhir_models/bootstrap/hashable.rb:69
- TodoComment lib/fhir_models/bootstrap/hashable.rb:108
- TodoComment lib/fhir_models/bootstrap/hashable.rb:109
- TodoComment lib/fhir_models/bootstrap/hashable.rb:117
- Recursive walk over a caller-supplied document has no depth cap lib/fhir_models/fhirpath/evaluate.rb:118
- Recursive walk over a caller-supplied document has no depth cap lib/fhir_models/bootstrap/hashable.rb:33
- Recursive walk over a caller-supplied document has no depth cap REDACTED:98
- Recursive walk over a caller-supplied document has no depth cap lib/fhir_models/bootstrap/xml.rb:34
- Recursive walk over a caller-supplied document has no depth cap lib/fhir_models/bootstrap/xml.rb:110
- FHIRPath.compute (cyclomatic 143) lib/fhir_models/fhirpath/evaluate.rb:70
- CommonStructureDefinitionCompare.compare_element_definitions (cyclomatic 65) REDACTED:248
- CommonStructureDefinition.verify_element (cyclomatic 56) lib/fhir_models/fhir_ext/common_structure_definition.rb:137
- ClassGenerator.generate_class (cyclomatic 35) lib/fhir_models/generator/class_generator.rb:37
- Model.validate_field (cyclomatic 30) REDACTED:175
- Template.to_s (cyclomatic 25) lib/fhir_models/generator/template.rb:48
- CommonStructureDefinitionCompare.compatible? (cyclomatic 23) REDACTED:12
- FHIRPath.get (cyclomatic 20) lib/fhir_models/fhirpath/evaluate.rb:16
- CommonStructureDefinition.check_binding_element (cyclomatic 19) lib/fhir_models/fhir_ext/common_structure_definition.rb:400
- Hashable.from_hash (cyclomatic 18) lib/fhir_models/bootstrap/hashable.rb:48
- IGLoader.load_ig (cyclomatic 18) lib/fhir_models/generator/ig_loader.rb:39
- InstanceXml.hash_to_xml_node (cyclomatic 17) lib/fhir_models/bootstrap/xml.rb:90
- CommonStructureDefinition.data_type? (cyclomatic 17) lib/fhir_models/fhir_ext/common_structure_definition.rb:324
- Hotspot: lib/fhir_models/generator/class_generator.rb lib/fhir_models/generator/class_generator.rb:37
- FHIRPath.compute (cognitive 321) lib/fhir_models/fhirpath/evaluate.rb:70
- CommonStructureDefinition.verify_element (cognitive 105) lib/fhir_models/fhir_ext/common_structure_definition.rb:137
- CommonStructureDefinitionCompare.compare_element_definitions (cognitive 70) REDACTED:248
- ClassGenerator.generate_class (cognitive 55) lib/fhir_models/generator/class_generator.rb:37
- Model.validate_field (cognitive 51) REDACTED:175
- CommonStructureDefinition.data_type? (cognitive 34) lib/fhir_models/fhir_ext/common_structure_definition.rb:324
- CommonStructureDefinition.check_binding_element (cognitive 33) lib/fhir_models/fhir_ext/common_structure_definition.rb:400
- Template.to_s (cognitive 27) lib/fhir_models/generator/template.rb:48
- CommonStructureDefinitionCompare.compatible? (cognitive 25) REDACTED:12
- FHIRPath.get (cognitive 25) lib/fhir_models/fhirpath/evaluate.rb:16
- IGResources.get_codes (cognitive 23) lib/fhir_models/generator/ig_resources.rb:90
- Hashable.from_hash (cognitive 22) lib/fhir_models/bootstrap/hashable.rb:48
- InstanceXml.hash_to_xml_node (cognitive 22) lib/fhir_models/bootstrap/xml.rb:90
- ClassXml.xml_node_to_hash (cognitive 21) lib/fhir_models/bootstrap/xml.rb:23
- Model.validate_profile (cognitive 19) REDACTED:113
- Model.method_missing (cognitive 18) REDACTED:39
- Model.validate_reference_type (cognitive 18) REDACTED:250
- REDACTED
- FileTooLong: fhirpath/evaluate.rb lib/fhir_models/fhirpath/evaluate.rb
- Change coupling: json.rb ↔ xml.rb lib/fhir_models/bootstrap/json.rb:1
- REDACTED
- Duplicated block (28 lines × 3) lib/fhir_models/r4.rb:17
Minor — 25 finding(s)
- Orphaned file lib/fhir_models/fhir_ext/common_structure_definition.rb:1
- Orphaned file REDACTED:1
- Orphaned file REDACTED:1
- Orphaned file lib/fhir_models/generator/class_generator.rb:1
- Orphaned file REDACTED:1
- Orphaned file lib/fhir_models/generator/ig_resources.rb:1
- Orphaned file lib/fhir_models/bootstrap/hashable.rb:1
- Orphaned file lib/fhir_models/generator/template.rb:1
- Orphaned file lib/fhir_models/bootstrap/common_definitions.rb:1
- Orphaned file lib/fhir_models/bootstrap/xml.rb:1
- Orphaned file lib/fhir_models/fhir.rb:1
- Orphaned file REDACTED:1
- Orphaned file lib/fhir_models/generator/ig_loader.rb:1
- REDACTED
- REDACTED
- Further orphaned files (smaller)
- REDACTED
- No ADRs
- No architecture diagram/doc
- CI build step not evidenced
- No SAST REDACTED:6
- No dependency-update automation test/fixtures/us_core/package.json:10
- No changelog
- Duplicated predicate REDACTED:300
- Ruby's type checker does not check nil everywhere
Minor — 4 finding(s)
- Outdated: nokogiri
- Outdated: pry
- Outdated: rubocop
- Outdated: test-unit
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=0 --max-count=200" --report-format json --report-path /tmp/watchdog-gitleaks-3ecea8cac0524be6a6bf0900487ab11d/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=200 --max-count=312" --report-format json --report-path /tmp/watchdog-gitleaks-3ecea8cac0524be6a6bf0900487ab11d/history-1.json --exit-code 0 --source . | 2 | artifacts/raw/gitleaks-history-1.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=512 --max-count=60" --report-format json --report-path /tmp/watchdog-gitleaks-3ecea8cac0524be6a6bf0900487ab11d/history-2.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history-2.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-3ecea8cac0524be6a6bf0900487ab11d/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt --exclude lib/fhir_models/definitions --exclude lib/fhir_models/examples . | 12 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 3 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 0 | artifacts/raw/trivy-fs.json |