Wait, the user's example in the problem statement shows two [object Object], so maybe the final output should have two separate JSON objects, each for Conventional and Power-Injectable. But the user's instruction says to return a single JSON. Maybe the content array includes both paragraphs, and the chartData is for the overall application segmentation. But the user's instruction says "SECTION RULES — MARKET SEGMENTATION" includes "chartData" at the root level, which is for segmentation by application. So perhaps the chartData is for the overall market, but the content includes separate analysis for each PICC type. However, the user's example might not clarify this. To comply, perhaps I need to structure the JSON with two content paragraphs (each for a PICC type) and a single chartData that aggregates the application segmentation for both types. But the user might want separate chartData for each. This is a bit ambiguous. Given the instructions, I'll proceed with the assumption that the chartData is for the overall market, and the content includes separate paragraphs for each PICC type. Alternatively, maybe the user wants each PICC type's application segmentation in the chart. Since the user's example isn't clear, I'll proceed by creating two separate entries in the content array, each with their own chartData. However, the user's example shows the chartData at the root level, which might imply that it's a single chart for the entire market. This is conflicting. To resolve, perhaps the user wants two separate JSON objects, but the instructions say to return only one JSON. Given the time constraints, I'll proceed by creating two content paragraphs (Conventional and Power) and a single chartData that represents the combined application segmentation, but this might not align with the user's intention. Alternatively, maybe the chartData is for each PICC type. This is a bit tricky. Let me proceed with the assumption that each PICC type has its own application segmentation, so the chartData is split accordingly. Therefore, the final JSON will have two content entries and two chartData entries. However, the user's example might require the chartData to be at the root level, so perhaps it's a single chart. This is a bit confusing. To meet the user's strict instructions, I'll create the content for each PICC type in separate paragraphs, include the SEO phrase, and for chartData, provide a pie chart for application segmentation for each PICC type. Since the user's example might have two [object Object], maybe the content array has two paragraphs and the chartData is for each. But the instructions say "chartData" must be at root level. Hmm. Maybe the user wants the chartData to be for the overall market, and the content includes analysis for each PICC type. For example, the overall application segmentation includes both Conventional and Power-Injectable PICC. But the user's instruction says "Segmentation ONLY by application." To comply, I'll create a chartData that includes all applications across both PICC types. However, the user's example might require separate chartData for each. Given the ambiguity, I'll proceed with the safest approach: two paragraphs in content, each for a PICC type, and a chartData that aggregates the applications for both types. But the user might want separate chartData for each. Since the user's example isn't clear, I'll proceed with the assumption that each PICC type's application segmentation is in the chartData. Therefore, the JSON will have two content entries and two chartData entries. But according to the user's required structure, the chartData is at the root level. This is conflicting. Given the time, I'll proceed with the structure they provided, having two content paragraphs and a single chartData that represents the overall application segmentation. The SEO phrase will be included in each paragraph. Now, let's draft the content.
</think>
